Admittedly, this is way off topic for this blog, but the recently unveiled Tesla Roadster strikes me as an awesome feat of engineering.  They've married the ultra lightweight Lotus convertible chassis with a high performance electric motor & drive train along with a few thousand lithium ion batteries (the kind used in laptops) to deliver a politically correct and wicked cool electric sportscar. It gets Ferrari-like performance, goes 130 mph, runs on pennies per mile and has a range of 250 miles. Heck, it even has an ipod interface.  The only downside: it's going to costs close to $100K.  If it had luggage space, I might be able to rationalize it.  For the money-is-no-object crowd, this car will be unmatched.  But for the rest of the world, it will likely be …

I will be free for dinner on Tuesday evening, July 25th, and I’d love it if you’d join me! Watch this space for details, although the update will be Tuesday, likely late afternoon.

(and of course let everyone know I’ll be doing my “So you’ve inherited a MySQL instance on unix” workshop — how a beginner can find out info/security checklist for everyone — Wednesday at 4:30 pm.)

Starting MySQL 5.1 (1), we’re simplifying life when it comes to the number of builds for each platform. We will be building only one binary package for each platform (2): the binary known in MySQL 5.0 as “max”. The assumption is that users prefer one binary with all options enabled, rather than having to choose the proper version at install time (or worse still, rely on others having made the proper choice on their behalf).

And with only one version, there is no need to call it “max”. “The max version is dead. Long live the max version!“. Not to speak in riddles, the standard mysqld binary is intended to contain all mysqld-max features. While 5.1.11 e.g. in Linux (x86) package still has three binaries

mysql-5.1.11-beta-linux-i686/bin/mysqld
mysql-5.1.11-beta-linux-i686/bin/mysqld-debug
mysql-5.1.11-beta-linux-i686/bin/mysqld-max

the plan is to reduce this to two. …

Earlier this week I released the revamped Connector/NET documentation. This is part of the wider Connectors chapter rework, which I’m currently finishing by doing the Connector/J and Connector/MXJ documentation.

Connector/NET provides a full ADO.NET compatible interface to MySQL and is compatible both the Windows .NET and Mono installations.

read more

The MySQL Community toolbar have 450 downloads for few hours. This is an extremly good news.

Update
—————-
We have a new logo (for the extension storage) and 1 new menu with user options. The firefox will update your toolbar soon, or you can check for updates using your extension window.

Tools >> Extensions

Next week has two excellent tech conferences going on and I'll be splitting my time between both as well as trying to get my normal job done.  I'll be at Oscon in Portland Monday and Tuesday and then at the AlwaysOn Network conference at Stanford Wednesday and Thursday.  It's a shame the events aren't spread out further.  We have quite a few developers heading to Oscon including folks from engineering as well as our Community team.  And we'll have a few of the business folks at AlwaysOn. 

Matt Asay, chief business dude over at Alfresco has organized an executive briefing day known as …

MySQL 5.1 (which is in beta right now btw) will have an interesting new feature called partitioning which will allow for a bit more scalability in certain situations. You can read more about it here, here, and here.

I don't see this really being much of an advantage in practice. Most people want to scale their database in terms of transactions per second. You could buy three disks and put a partition on each or you could put the whole thing on a stripped RAID array. Each would have the same IO characteristics (assuming your …

Lots of people at MySQL like Skype, because they find it easier to use than straight VoIP. I'm not so happy:

• Skype is a proprietary protocol. Sure, they're charging hardly anything for it—at the moment. But once you're locked in to that kind of protocol, it's difficult to change. I doubt that Skype will ever get really expensive, but there's a danger.
• For a dyed-in-the-wool computer person like me, using GUIs to interface is counterproductive. Would you want a telephone with a mouse on it? Probably not. Then why do that with a modern replacement? I'd be much happier with a command line interface which enables me to do things like:

  skype> call Caltabvin Sun
  

  Here the text in bold is that I enter (Cal), and the tab completes the name. So much easier than scrolling through menus with names or even photographs. …

After getting tired of waiting for the MySQL folks to add features to FULLTEXT and to make it work on InnoDB, I decided to do it myself. I’ve just finished sqlsearch 1.0.0. Features:

• ENGINE-independent (requires triggers)
• Uses fast, full-word indexed searching
• Multi-table and multi-column indexes supported
• Supports “quoted strings” and +/- logical operators in search queries
• Gives search query feedback, including why some terms were ignored
• Provides typo and phonetic suggestions for words which don’t appear in the index
• Supports weighting of “sources” (tables or fields) and “ids” (rows)
• Supports link information …

In the deadlock section, innodb shows:


what the last deadlock was

what the deadlocks state was

what the deadlock lock was holding

and what they were waiting for


060718 8:00:18
*** (1) TRANSACTION:
TRANSACTION 4 4095301271, ACTIVE 0 sec, process no 19925, OS thread id 387040248038 starting index read
mysql tables in use 1, locked 1
LOCK WAIT 2 lock struct(s), heap size 368
MySQL thread id 2287022118, query id 5904669207 [HOST] [user] Searching rows for update
/* /PHPFILE: PHP FUNCTION() */ UPDATE Latest SET `date_create`='?', `id`='?' WHERE user_id=?
*** (1) WAITING FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 0 page no 6669281 n bits 608 index `user_id` of table `DB/Latest` trx id 4 4095301271 lock_mode X waiting
Record lock, heap no 38 PHYSICAL RECORD: n_fields 3; 1-byte offs TRUE; …