Well this past weekend we attended a local colleges seminar on admissions and financial aid that really opened her eyes to all the things she needs to be doing. Since then we have filled out her FAFSA, the states version for financial aid, started looking at scholarships/grants to apply for, and scheduled her ACT and SAT tests.

She still has quite a bit more to do to have everything done in time, but at least she has started.

If you are considering submitting to the conference, I highly suggest you get a move on it. You have a little less then a week to do it (Call closes 11:59pm 01/27/2010 PST. ). You can submit a talk for the MySQL User Conference here. For information on registration for the conferences go here.

I have submitted my site for the campaign and wanted to pass the word for others to join. I hope you will join us when we “Go Pink”.

Anyway after a bit of quick digging we found CREATE TABLE … SELECT and CREATE TABLE … LIKE. Both can do the job (with a little help), just in different ways.

CREATE TABLE … SELECT will not automatically create any indexes for you, so if you want to have indexes in the created table, you should specify these *before* the SELECT statement. This means you will have to already know what the indexes are and how they are declared before issuing the command – but you can load the table at the same time.

CREATE TABLE … LIKE will create an *empty* table based on the definition of another table, including any column attributes and indexes defined in the original table. To load it, another command will have to be given (INSERT … SELECT).

Oh and before you ask – you can’t use both … syntax error

So which way would you go – and why? Also if you can think of another way to do this (purely SQL) – feel free to educate me.

1) Did you know that NULL and empty string “” can be valid elements of an ENUM column – even if they are not explicitly named!

From the ENUM manual page:

The value may also be the empty string (”) or NULL under certain circumstances:
* If you insert an invalid value into an ENUM (that is, a string not present in the list of allowed values), the empty string is inserted instead as a special error value. This string can be distinguished from a “normal” empty string by the fact that this string has the numerical value 0. More about this later.

If strict SQL mode is enabled, attempts to insert invalid ENUM values result in an error.

* If an ENUM column is declared to allow NULL, the NULL value is a legal value for the column, and the default value is NULL. If an ENUM column is declared NOT NULL, its default value is the first element of the list of allowed values.

2) The mysql command line utility can ignore statements except those for the default database named on the command line using the –one-datebase option.

This is can be extremely useful for skipping updates to other databases in the binary log or a backup mysqldump file. Wish I knew about this years ago.

Ex:
shell> mysql -uroot -ppwd --one-database db1 < /path/backup.sql

3) In 5.1 with InnoDB you can reduce DML locking by using the READ_COMMITTED isolation level. Harrison, one of my senior colleagues, even blogged about it.

Until then, I thought that the isolation level dealt only with the reading of data and had nothing to do with the locking of it. My ignorance was exposed to the light and I am still wrapping my brain around it, but I think I have finally gotten used to the feeling now.

Just when I think I have the basics - something little comes along to knock me back into my place. Anyway - back to work!

For 2009 I was supposed to try and meet a couple of personal and professional goals. Some of the goals I like to think I have met include:

1) relearning how to balance my work and family. When I started working at MySQL I felt so completely inadequate in my new role that I completely submersed myself in it to try and get myself to someplace that while not comfortable, at least didn’t leave me feeling stupid all the time. I found that place after about a year, but by then I was so consumed with work that I had little time for anything else. 2009 was the year I wanted to take back my personal time.

Now that I have again found that balance, for 2010 I want to get back to my roots and turn my hand back to so PHP coding again. I am massively rusty, but I do miss it so it should be fun.

2) speaking at conferences. I am always telling people to submit talks to conferences but never seemed to have the time to do it myself. Yes I was being a hypocrite.

For 2009 I swore I would submit talks to any conferences I thought I might actually be able to get the time off of work to attend and as luck would have it – they liked me… They really liked me. Crazy people – must be stoned or something.

In 2009 I was accepted to speak at 5 conferences (6 if you include the Microsoft summit) and after being ill before the first one – had a fantastic time. I will definitely be continuing this for 2010.

I have been honored to already be accepted to speak at this years spring conferences – TekX and Confoo. Unfortunately though I have had to withdraw from the Confoo conference due to work requirements, but I will be attending TekX in May. And if I am brave enough, I am also going to try and submit to the MySQL User Conference.

3) install solar panels on the house to reduce our carbon footprint and our electricity bill. Took us a while but it is finally done. The solar panels are in and the solar water heater is working. We are currently waiting for the local electric company to come and install a 2 way metering system.

4) Help my daughter. While not on the original 2009 TODO list, it immediately went to the #1 slot when her father passed this fall. This will be an ongoing thing that may never have an end. But she is worth it.

5) hold semi-regular meetings for the PHPWomen board. Trying to coordinate 7+ people around the globe for meetings is a pain – but we managed to do it a number of times this year to discuss ideas, catch up on projects and touch base with everyone. Not bad.

Ok – time for the listing of things I did not do this year that I wanted to. This list could easily be couple of pages long but we will shoot for a condensed version.

1) get back into writing. I love to write and for some reason, just haven’t had cause to write in a while. Need to contact some people to see if they need any new articles… Wonder if E3 would let me do something for PHPArch maybe…
2) didn’t learn enough for work – still need to get more into performance tuning, benchmarking, cluster and server administration. Always so much to learn, and never enough time (remember trying to balance work/life).
3) PHPWomen – oh let me count the ways… I really wanted to have the paperwork filed for 501c3 this year, never quite made it. Wanted to also have a birthday party for PHPWomen during Zend Con but due to unforeseen circumstances that didn’t happen… also forgot to try and have a “Go Pink” drive for breast cancer.
4) help get the PHPCommunity organized with the provisional board. laying the foundation for hopefully better to come.

This listing can keep going on and on – but now seems like a good time to stop. Here is to hoping 2010 is a great year!

If you find any bad links/posts please let me know so I can fix them. And tell me what you think of this new theme.

I think I have finally managed to get my blog up and running again (only been about a year) since I keep being told by people that “it doesn’t work” and well … because I really need to get back to blogging. I hate always talking to myself and that seem to be all I have been able to do lately. Much more fun to babble in your ear.

Anyway – lots of stuff going on and will get to that later, but for now – Happy New Year everyone.

Hmm – Guess I can check off “Fix Blog” from my 2009 TODO list (hey be nice I am only a day or so late).

Edit: seems a number of my links are broken right now. I will be fixing them over time.

While there I will also be presenting 2 talks on MySQL – one on MySQL server tuning and the other on EXPLAIN. I admit it – I love MySQL optimization. If you do too, be sure to join me though I am admittedly.. kinda upset that I will be opposite Lorna’s talk on using and understanding open source communities. That was one talk I wanted to attend myself. If I am lucky she will let me look over her slides afterwards