I decided I’d be a good sport and try to do some build work for Drizzle on OpenSolaris to make sure we weren’t accidentally Linux-ifying something. Nevermind OpenSolaris installing an nsswitch file set up to not use DNS by default. Nevermind OpenSolaris reinventing the wheel for package management rather than starting with a package management system already in use by people (or and then fixing the things . Nevermind the GPL incompatible CDDL license… I’d be a good sport and give it (another) try.

I should add, in all honesty, I really do want OpenSolaris to be good. I think monocultures are bad, and I think Solaris can be useful in the growth of the ecosystem.

Step one. Install bzr.

pkg search bzr

Nothing. Wasn’t expecting much. That’s ok. Grab tarball. Unpack.

FAIL

Silly me. There is no sudo, so I had become root first (sure - I’m sure there …

If you decide to copy over one table from MySQL installation to another installation, this could be done as simple as copying over your-table-name.\* in data directory. Ofcourse, to do this, the database should not be running at the time of copying.

For example, for tables created by MyISAM storage engine, the files to be copied for table mytable are mytable.frm, mytable.MYD and mytable.MYI. The ".frm" file contains table definition, the ".MYI" contains info about index and ".MYD" contains data.

If you do this kind of stuff often, you may want to dump the header of the ".frm" header file. I just wrote a script for this. You can download this php script "frmdump" from here. Note that it is a php script, but meant to be run from command line (not to be used as web page) :

   $  ./frmdump   mytable.frm
  
Dumping  mytable.frm using .frm header format ... …

If you decide to copy over one table from MySQL installation to another installation, this could be done as simple as copying over your-table-name.\* in data directory. Ofcourse, to do this, the database should not be running at the time of copying.

For example, for tables created by MyISAM storage engine, the files to be copied for table mytable are mytable.frm, mytable.MYD and mytable.MYI. The ".frm" file contains table definition, the ".MYI" contains info about index and ".MYD" contains data.

If you do this kind of stuff often, you may want to dump the header of the ".frm" header file. I just wrote a script for this. You can download this php script "frmdump" from here. Note that it is a php script, but meant to be run from command line (not to be used as web page) :

   $  ./frmdump   mytable.frm
  
Dumping  mytable.frm using .frm header format ... …

As Matt Asay recently mentioned in his post about Kickfire, the company just closed a Series B for $20 million. In today’s credit-scarce market where VC funding is flat/declining, $20 million is a lot of money, especially for a company whose product is still in beta. What’s more, there seems to be an investment bubble in the broader data warehousing space in which Kickfire participates (at last count, there were over two dozen vendors, the majority of which are relatively new entrants) and that bubble looks like it is starting to burst as witnessed by Microsoft’s recent acquisition of DATAllegro. So, are the Kickfire investors misguided or is there something more here …

We prepared RPMs of our release for RedHat 5 / CentOS 5 x86_64 platform.
http://www.mysqlperformanceblog.com/mysql/RPM/RHEL5/5.0.62/

There was question what patcheset includes and if there is manuals.
We have:

• microsecond resolution in slow-log
• extended query plan in slow-log and InnoDB statistics. You can read more here http://www.mysqlperformanceblog.com/2008/04/20/updated-msl-microslow-patch-installation-walk-through/
• User / Table / Index statistics (Google's patch). More here …

Before I am leaving for my summer vacation I wanted to share the first screen designs for the Mac version of Workbench. Click on the small images below to view the screenshots at full size.

The first shot shows the new Overview Page. It holds the Workbench Central panel (that can be collapsed of course), the Machine-Group panels and a Notes panel. Each machine tab holds a list of Database Connections and MySQL Models that are associated with that particular machine. (The list of Database Instances shown in this screenshot - which will give you access to administrative features - are a WB 6.0 feature coming later next year).

When you double-click a Database Connection you will get to the new SQL Query interface that is show on the next screenshot. When a MySQL Model has been double-clicked the model is opened on a new main-tab …

Due to summer vacations - yes, even we take some time off - our release-cycle has slowed down quite a bit so it has already been more than 4 weeks since we aired an update of Workbench. Right in the middle of testing and preparing the next build, our build-server has raised the white flag. Looks like the cooling system above the unit decided, that its too hot, and put a cold shower right down on our machine. Our engineers are quickly gathering some new iron and we are meanwhile preparing the build manually this time. There are a few bugs remaining but next package will be ready soon and we put it on our download servers - so stay tuned for the next Workbench 5.0 release.

So, the Malta MySQL User Group has had its first ever meet-up today, and it was a success! When organizing it, I had no clue how many people would show up, people have said “yes” and then changed to “no”, and vice versa.

Anyway, so the morning came, and I sent out a few confirmation emails, and it suddenly dropped down to just three of us, which was a shame. Anyway, around 5pm, I noticed that there was four more that had just said they wanted to attend. Unfortunately, one of those dropped out, but it was still a great turnout.

This is a great opportunity for us to promote MySQL use in Malta, as well as share experience and knowledge. Also just to network a bit.

So, this time, for meeting #1, we met up outside a local bank, and walked to Il-Mithna, which is a local restaurant. In this picture, there is the first core group of local user group members, all happily gathered and just about to start our discussions. …

We are quickly approaching opening up the MySQL Query Analyzer for general beta and I wanted to pass along an open invite to the following related and informational events.

On 8/13, I will be doing a micro level presentation on MySQL Enterprise. Please attend and learn more about the database software, monitoring and advisor services and support solutions that make up a subscription. I plan to do a demo of the Enterprise Monitor and the new Query Analyzer; that alone makes attending worth the price of admission (in this case 45 minutes of your time!). Learn more and register here.

On 8/20, I will be doing a presentation on the new Query Analyzer. This will be a technical discussion around how DBAs monitor for bad queries now and how the Query Analyzer makes the job much easier. This will be a good time to learn about getting in …

Why may LIMIT only take a fixed number? Not even a user variable, let alone an expression.

Wouldn't it be useful to set a user session variable that always gets applied as an implicit limit value?

Both of these things could be done in Drizzle.