I've been reading through the comments on the Slashdot article from yesterday and I found
this gem:
one of my biggest pet peeves of MySQL... when I say CREATE
TABLE(varchar(255) blah NOT NULL) please do not add your own
'DEFAULT ""' to the end--it is considered by some to be rather
rude! I can spot MySQL schema's a mile away by this single trait.
Anything NOT NULL almost always has a bullshit default value. Got
a NOT NULL int--it will have a DEFAULT 0! Got a NOT NULL date,
"DEFAULT 0000-00-00", which isn't even a valid date! How is that
for taking your data seriously?
I have always agreed with the above. When we set out to create
the "strict" mode within MySQL we could never get agreement on
the above sort of problems. Personally I have despised this stuff
for over a decade. I know where they come from, aka the
limitations of …
Check out the ideas from MySQL for Google Summer of Code 2009!
These are specially-selected projects for students who are looking to do some coding in a real, open-source, highly-adopted software environment.
The learning experience will be tremendous given that MySQL engineers will be mentoring them.
Some student stipend is provided by the Google Summer of Code. It is intended for students to gain "exposure to real-world software development scenarios and the opportunity for employment in areas related to their academic pursuits."
Check out the ideas from MySQL for Google Summer of Code 2009!
These are specially-selected projects for students who are looking to do some coding in a real, open-source, highly-adopted software environment.
The learning experience will be tremendous given that MySQL engineers will be mentoring them.
Some student stipend is provided by the Google Summer of Code. It is intended for students to gain "exposure to real-world software development scenarios and the opportunity for employment in areas related to their academic pursuits."
Sometimes people ask why do I use MacOSX as my main work platform (isn’t that something to do with beliefs?). My answer is “good foundation with great user interface”. Though that can be treated as “he must like unix kernel and look&feel!”, it is not exactly that.
What I like is that I can have good graphical stable environment with some mandatory tools (yes, I used OS-supplied browser, mail, etc), but beside that maintain the bleeding edge open-source space (provided by MacPorts).
Also what I like, is OS-supplied development and performance tools. DTrace included is awesome, yes, but Apple did put some special touch on it too. This is visualization environment for dtrace probes and other profiling/debugging tools:
Even the web browser (well, I upgraded to Safari4.0 ;-) provides some impressive debugging …
[Read more]The numerous popular MySQL forks are an unexpected consequence of Sun's acquisition. But why haven't we seen any JBoss forks since the Red Hat acquisition? READ MORE
Some months ago, Google released a patch for InnoDB that boosts performance on multi-core servers. We decided to incorporate the change into the InnoDB Plugin to make everybody happy: users of InnoDB don’t have to apply the patch, and Google no longer has to maintain the patch for new versions of InnoDB. And it makes us at Innobase happy because it improves our product (as you can in this post about InnoDB Plugin release 1.0.3).
However, there are always technical and business issues to address. Given the low-level changes in the patch, was it technically sound? Was the patch stable and as rock solid as is the rest of InnoDB? Although it was written for the built-in InnoDB in MySQL 5.0.37, we needed to adapt it to the InnoDB Plugin. Could we …
[Read more]Many InnoDB scalability problems seem fixed in InnoDB-plugin-1.0.3 and I expect InnoDB-plugin will run fine on 16-24 cores boxes for many workloads. And now it is time to look on systems with 32GB+ of RAM which are not rare nowadays. Working with real customer systems I have wish-list of features I would like to see soon:
- Fast recovery. Both recovery after crash and recovery from backup can take unacceptable long time, especially if you crashed with full 32GB buffer_pool. There is reported bug http://bugs.mysql.com/bug.php?id=29847, with ETA MySQL-6.0
- Preload table / index into buffer_pool. You can use custom queries by primary / secondary key to "warm up" part of table, but this solution is ugly and may be slow due to random logical I/O. Implementing preload of full .ibd file with sequential read would be much better solution. This is actually more …
The annual MySQL Conference & Expo will be held in this year on April 20-23 in Santa Clara, California with a double twist.
Not one, but *two* FREE additional MySQL Conferences are running at the same time, in the same hotel. If you on the west coast you can effectively get a free conference with many MySQL experts speaking at them. I am speaking at all three on three different topics.
The first announcement was the 2009 MySQL Camp organized by Sheeri K. Cabral - The She-BA in line with the O’Reilly approach of having a smaller un-conference within a conference such as with Web 2.0 NY last year.
However the big news was the …
[Read more]