Added a new option/report: Distribution of Total Questions (--dtq or --tdq or just --dq) which shows of all the questions/queries what percentage are DMS (selects, inserts, updates, etc.), query cache hits, other Com_ status vals, COM_QUIT, or Unknown. I use this as a quick first-glance way to see what a MySQL server is busy actually doing. There are 6 new example reports which show that some servers are busy doing nothing. Ideally, you'd hope your MySQL server was primarily busy with DMS and qc hits.

mysql is looking to hire a community relations person in the united states.

oh, and the mysql users conference 2006 was announced, and the call for papers is out. the deadline for submissions is november 7.

Hey all,

Here is the rough outline for the upcoming Synchronization Manager article. I expect to have it fleshed out and ready for publication by the end of next week or shortly thereafter. Please give feedback if you see anything missing or are not interested in particular topics.

Thanks!

• 
  
• Concepts
  
  • 
    
  • Replication Units
    
    • 
      
    • Master Unit
      
    • Client Unit
      
    • Activating Replication Units
      
    
    
  • Message Server, msgserver
    
  • Synchronization Service, syncservice
    
  • Conflicts
    
  • Table name mapping
    
  • Master database …

I read with interest Zack Urlocker's blog entry for today on his experience with a new Intel based Mac MySQL have recently got their hands on. I was looking for a new PC at the start of the year, maily because of some problems with my current windows box having problems communicating with various USB devices. I've always liked the look of Macs but the expense has always put me off, I'm not made of money after all.

But lucky for me (and apple), my looking for a new PC coincided with Steve Jobs announcment of the Mac Mini. Anyway I'm sure you're not interested in my shopping habits so on to the important part.

I purchased the Mac Mini to develop my website www.mysqldevelopment.com (shamless plug) on, that meant I needed some html writing software, an FTP client and of course a MySQL database. One of the great things which became apparent straight away was …

A couple of weeks ago, MySQL got our first Intel based Macintosh machines.  Very cool!  Unlike Adobe's expereince, in just a few hours, we were able to recompile MySQL 5.0 beta using the standard GCC compiler, get it linked with the appropriate Mac Intel libraries and get the server up and running.  So far, performance is fantastic!  (And this is a beta release on a beta platform!) (Actually, we've also been able to run MySQL on Longhorn with a recompile, so perhaps this has more to do with our code than with the platform itself.) 

Nonetheless, the Mac platform has won a lot of hearts and minds of open source developers.  At any open source conference, I see a ton of Mac laptops since it's running Unix with a great GUI.  A lot of our developers at MySQL are absolute Mac heads and I think we'll …

MySQL 5 is still beta (today, September 23, 2005) and we, the users, don't know when it will become stable. However, some clues are starting to mount, and by putting things together we can try to foresee when this event will take place.

One of such clues is the recent release of a new book, MySQL® 5 Certification Study Guide, the official guide to the exam to become a MySQL certified professional.
The book is available at major bookstores. I am still waiting for my copy from Amazon, but in the meantime I was able to read the interesting parts in Safari. The news are that there are no longer a Core and Professional Certifications. Now there are two certification paths, Developer and DBA, each of which require two exams to get the title.

Therefore, in the new course, rather than holding a "core certification" or a "professional certification", you can get :

• MySQL Developer I
…

Found on Flickr:


The photo was taken by Kevin Severud, who also happens to be the proud owner of the plate.
Kevin notes:

It's all mine. It's my way of honoring what I consider the preeminent tool of the masses to make the information age a reality. But it's also my way of honoring my Swedish heritage (jeg er kvart svensk og halv norsk).

Tack, Kevin!

You've probably already read about this in other people's blog entries.... I now have my own dedicated VP Community Relations! Only for a short while really, because more people are joining our community department. Which is fab also.

Anyway, Kaj Arnö by no means a stranger to community work, and posesses just the right degree of nuttyness required for this job ;-)

He knows Monty, David (co-founders) and Mårten (CEO) from way back, started the MySQL Training program, and actually was my first boss when I joined the company in 2001, doing Documentation and Training. He has since done excellent work VP'ing various departments, and will now give Community the additional resources and enhanced profile at the highest level. It's going to be great, with lots more cool stuff happening on the MySQL Community front.

Kaj is already scribbling in his …

Yes, it was my daughter Phoebe next to the userconf banner ;-)

Phoebe is now three months old, and doing great!
The little T-shirt is the only one of its kind, I am researching MySQL merchandise so this was a fun test subject (the colour is a bit off, and the method of printing not quite the way I like it... so you don't want to be asking me where I got this exact one).
The banner comes from the 2005 conference, the main speaker stand. As prog chair, I was allowed to take it home all the way to Brisbane Australia. Luckily it's small enough to fit into a suitcase...

Today is where the rubber meets the road in the Oracle/MySQL comparison; locking and transactions. At the end, I'll give you a little Oracle fun.

As I said yesterday, the different storage engines may or may not support transactions. MyISAM tables do not support transactions while InnoDB tables do. First, I create two tables; one as InnoDB, one as MyISAM:

system@localhost:world> create table city_myisam 
   engine = myisam as select * from city;
Query OK, 4063 rows affected (0.78 sec)
Records: 4063  Duplicates: 0  Warnings: 0

system@localhost:world> create table city_innodb 
    engine = innodb as select * from city;
Query OK, 4063 rows affected (0.53 sec)
Records: 4063  Duplicates: 0  Warnings: 0

Next, I set autocommit off.

system@localhost:world> set autocommit = 0;
Query OK, 0 rows affected (0.06 sec)