|
|
If you are in the Los Angeles area, you have two more chances to meet the MySQL gurus on their way to the the MySQL Conference. Today at the USC, Sheeri and I will conclude the South California MySQL Campus Tour. Tomorrow, April 17, big gathering at the Los Angeles MySQL Meetup Group, where Andrew Aksyonoff, Sheeri, and myself will be the speakers. Come along! |
During the event, I will do …
[Read more]Q4M 0.8.5 is now downloadable from q4m.31tools.com. Prebuilt binaries for MySQL 5.1.33 running on linux (i386 or x86_64) and Mac OS X 10.5 (x86) are available as well.
There are no bugfixes in this release. The only change from version 0.8.4 is bundle of boost header files necessary for building Q4M. The build process no more requires separate installation of the Boost C++ libraries.
If you are going to load a lot of records into Cluster, don't
forget to set max_rows!
My colleague, Yves at BigDBAhead, has also blogged
about this, but I also ran into the same problem recently.
I did try to populate 100M records on a 4 node cluster, and the
data nodes went down with the following error message in the
error logs:
"2304 Array index out of range"
So the error message is crap - and my opinion is that there
should be a proper error message propagated up to the mysql
server. There is a bug
report on this.
Simplified, what the error message means is that you have run out
of "index slots" in the Hash Table storing the hashes of the
Primary Keys. This is because each table is divided into a number
of partitions, and each partition …
Giuseppe Maxia and I are in the exact middle of our leg of theMySQL Campus Tour. Yesterday’s session was recorded — play the video online right in your browser at http://technocation.org/node/700/play or download the 80 Mb .mov file at http://technocation.org/node/700/download.
A PDF of the slides can be downloaded at http://technocation.org/files/doc/2009_04_Tour.pdf (21 Mb).
Click on the thumbnails for larger pictures of the standing-room
only crowd, and lunch with the great folks at Cal Poly
afterwards:
…
|
|
The second leg of the Southern California MySQL Campus Tour was at UCLA. There was less attendance than Cal Poly. Only 22 brave souls who endured a lengthy session with a long tail of Q&A. The excitement came on my way back to my hotel, 25 miles from the campus. Distances have a different meaning here. A few dozen miles is just a tiny portion of the town, and so I found myself once more driving the endless highways of Los Angeles. |
When I was almost home, I saw all the cars in front of me stopping, for what I …
[Read more]We have an ongoing Drizzle milestone called low-hanging-fruit. The idea is that when there’s something that could be done, but we don’t quite have the time to do it immediately, we’ll add a low-hanging-fruit blueprint so that people looking to get a start on the codebase and contributing code to Drizzle have a place to go to find things to do.
Some of my personal favourites are:
[Read more]With the introduction of MySQL Connector/C++, now C++ application developers have one additional option to choose from, to connect to MySQL Server 5.1 or later from a C++ application. Admittedly, as of today, there isn't enough documentation with examples to show the capabilities [and gotchas] of MySQL Connector/C++. I tried to fill that gap with the technical article, Developing Database Applications Using MySQL Connector/C++. Hopefully it serves as a starting point for the C++ developers while waiting for the MySQL Connectors documentation team to publish the official documentation on MySQL Developer Zone.
While you are at it, don't forget to check the supplement document, Installing MySQL Connector/C++ from Source, in case if you …
[Read more]Restoring a single database from a full dump is pretty easy, using the mysql command line client’s --one-database option:
mysql> mysql -u root -p --one-database db_to_restore < fulldump.sql
But what if you don’t want to restore the database, you just want to extract it out of the dump file? Well, that happens to be easy as well, thanks to the magic of sed:
shell> sed -n '/^-- Current Database: `test`/,/^-- Current Database: `/p' fulldump.sql > test.sql
You just need to change “test” to be the name of the database you want extracted.
We’re having a Drizzle Developer Day just after the MySQL Conference and Expo next week. You don’t have to be attending the conference to come to the Drizzle Developer Day. Just bring your enthusiasm for free databases, Drizzle and good software. Spaces are limited, so head on over to the signup page and fill in your name if you haven’t already
If coming from the Hyatt Regency Santa Clara (where the MySQL Conference and Expo is), at least I will be driving from there, so let me know if you want a lift.
"I was surprised for example to hear from Jay that the Drizzle
team should not compare its performance to MySQL only to Drizzle
itself"
This quote came from a piece of email today asking me about why
we, as in the Drizzle project, have not been publishing
comparison benchmarks.
First of all, this is not a Sun request, this was a request from
me to the other core members of the project.
Let me explain...
I don't think projects can ever objectively compare themselves to
other projects. Look at all of the heat that went on for years
between Postgres and MySQL. I think we, the Drizzle Project, are
better off publishing code and helping others create benchmarks,
but avoiding doing the comparisons ourselves.
We are inherently biased.
One of the first things that went up on the Drizzle wiki were the
pages that were labeled "this is not what we are". Namely we …