MySQL made some tasks from their internal task tracking tool - Worklog a while back. I just have not look at it besides checking Maria related tasks until couple of days ago as Jay announced new Forge going live.
Check it out - there are a lot of nice ideas out where. I can find a lot of things I originally submitted something like 5 years ago out there

I contributed most ideas during my first years at MySQL, some on my own some reformed customer suggestions from Sales/Support/Consulting engagements I was on. Later I practically stopped because there were not much attention to those small little convenience things - MySQL was on the road to take over enterprise market and all resources were focused on big things which allow to sell things to these customers.

In the recent months we're seeing MySQL is …

Top marks to Jay Pipes for getting the Forge 2.0 finally out after quite some time, as well as in the midst of the MySQL Conference he is organizing.

I am worried however about some of the content, as shown in the screenshot below, the opening page lists Worklog tasks/features for versions 6.x or 7.x , that’s ok, but features in 9.x. Where is the practicality of thinking more then 2 releases ahead, and just having a future bucket. Indeed, we have 5.1 and 6.0 already frozen and not releases, so 6.x is already 3 releases out.

Tonight we were told at the NY PHP Meeting MySQL 5.1 is not due to late Q2, so that’s at least June 2008.
The …

Tonight’s New York PHP community meeting was a talk by Philip Antoniades the MySQL Systems Engineering Manager.

With an interesting topic opener “A New Hope” I could not resist to hear Philip’s official MySQL presentation.

Some small points I took away from the presentation.

• Sun is committed to Postgres with Josh Berkus and a team of 20 people.
• Solaris.next is the next version of Sun, I thought that was a cool internal name, be it obvious
• A marketing slide of the highest traffic websites listed Meebo, yousendit, alexaholic, techcrunch, feedburneer, istockphoto and vimeo as reported by Pingdom. Not sure were they get their data, but Google, Yahoo, FaceBook, Wikipedia, MySpace, Fotolog are sites I think of as high traffic. Indeed 3 of these listed sites I’ve never heard of. …

NOTE: Any comments in this blog entry is based on my personal thoughts after visiting the Hadoop conference and doesn't represent any current plans within MySQL.

I visited the Hadoop conference today which was a very interesting event. The room was filled to its limit, people were even standing up in lack of chairs. Probably around 300 people or so.

It was interesting to see the wide scope of web-scale problems that could be attacked using Hadoop. The major disruptive feature in Hadoop is the MapReduce solution to solving parallel data analysis problems.

One piece that I started thinking of was how one could introduce the MapReduce into SQL. One presentation of HIVE showed an interesting approach of how to solve this problem. I thought a bit on how one could integrate a MapReduce solution in MySQL and there are certainly a lot of problems to solve but I got a few interesting ideas.

The …

Recently I acquired Sesame Street Volume 1, and on the third DVD in the set I came across one of my favorite Sesame Street songs: “Who are the people in your neighborhood?”

Here’s a sample of one such skit, if you are not familiar with it, or if you want a bit of nostalgia http://youtube.com/watch?v=B9lpUjQvToY (note, play will likely start automatically, so tune your volume appropriately before clicking).

The refrain is “Who are the people in your neighborhood? The people that you meet each day!” I live in a city of 34,000 people just 6 miles northwest of Boston, MA. I know exactly one neighbor, across the street, whom we met because I sent my husband over to get her live band to stop playing loud music at her party at 2 am. I do not know many of the local business owners. I do not know who lives in my neighborhood, yet people live around me. Saying I …

Navicat For MySQL is a GUI for MySQL developers. I've tried a few tools before but somehow got attached to Navicat due to a few nice features that I'm not going to go into right now. Navicat suffers from a couple of annoying bugs and random crashes. I don't know if I can help fix the random ones but if I can at least file the ones I can reproduce, everyone wins. I have the latest as of today version 8.0.23.

Bug [NAL-15328]: Structure Sync Fails to notice encoding differences

Lots of people like PERL, Python, Java or C to write database backfills, data repair, etc. I like writing in all these languages but what I don't like doing is writing the same code over and over again, so I write my DB code in the same language as the environment that I'm using. This means I write backend DB scripts in PHP, I get to reuse common DB paths, classes and functions and improve things when I see them.

But, PHP if not written correctly will use up 2GB of memory easily from loosing reference to arrays or setting globals and forgetting about them; stuff like that. This is especially visible in long running applications.

PEAR is not immune to these memory leaks. So, to get around reference problems in PEAR I do

$skiptrace =& PEAR::getStaticProperty('PEAR_Error', 'skiptrace');

$skiptrace = false;


This prevents this error
PHP Fatal error: Allowed …

Effective April 1, I will join Percona full-time as a consultant. I’ll be helping people build high-performance applications with MySQL, but I’ll also be continuing to develop and improve tools such as Maatkit. This career change has been a long time in progress. I’m really looking forward to it, but at the same time it’s hard to leave my current employer, The Rimm-Kaufman Group (RKG). Working with them has been the best job I’ve ever had.

The details can be found

http://en.oreilly.com/mysql2008/public/schedule/detail/588


I've since moved on from Flickr to a new Job, but Flickr is still allowing me to give this talk. Flickr is so cool!

The talk encompasses capacity planning and scaling for a heavy concurrent write and read environment, and when it makes sense to split resources out to a single application.

There was a proposed project of particular interest to me in the MySQL list for Google's Summer of Code, an Obfuscator. This tool would take a schema/dataset and obfuscate it in such a way that it can be posted on forums or submitted to MySQL in a bug or support request, without divulging any sensitive information.

If you're currently a student and want to work on this project and thus be an active part of the Google Summer of Code 2008, apply quickly (before March 31st) through the GSoC student application form and also join the MySQL SoC mailing list!

The Obfuscator …