While we're on the topic of Bazaar - this week I got informed by the organizers of the FrOSCon 2008 conference that they accepted two of my talk proposals: one session will be an introduction to this source code management system (what a coincidence), the other one will be an introduction to OpenSolaris for Linux users, explaining some of the underlying technologies and how they differ from what a seasoned Linux user may be accustomed to.

And no, I have not given up on using Linux - quite the contrary! I have been very impressed by the latest OpenSUSE 11.0 release and already run it for since quite some time on several of my work systems. In fact, I already convinced several colleagues of mine to …

Are you deploying your JRuby-on-Rails applications on Solaris (or any variety of Unix) and not able to connect to the database ?

I experienced it last week so thought of sharing the tip here. Luckily it's really simple.

Here is the default generated "config/database.yml"

The only required change is to add "host: 127.0.01" for the required database configuration. The updated fragment is shown below (with change highlighted):
…

Why one may wonder, it's just Swedish beer (State of Doplhin, MySQL UC 2006).
One week ago Jim Starkey sent message http://www.firebirdnews.org/?p=1742 so he will not work for MySQL anymore and starting new project. While that's fully Jim Starkey's personal decision, I expected some comments about Falcon future development from MySQL / Sun side. Jim was not just ordinary developer, but lead of project and main architect of Falcon and his leaving may change a lot. For now MySQL's calm seems stunned or indifferent to Falcon's destiny.
Falcon has being developed for about 2.5 years, and despite it named "beta" stage, it sill crashes in our quite simple benchmarks, so it's very optimistic "beta". That's why I wonder if this project will be ever finished, especially when main architect left it. …

Removing Barriers to the Community - MySQL Moves to Bazaar - Jay Pipes It is the role of a community manager to remove the barriers — both technical and ideological — between the user/developer community and the company or group of individuals which produces the open source software

Linux.com :: Lessons learned from NCSU FOSS class As textbooks, [...]

My post on what it’s like to write a technical book was a stream-of-consciousness look at the process of writing High Performance MySQL, Second Edition. I got a lot of responses from it and learned some neat things I wouldn’t have learned if I hadn’t written the post. I also got a lot of questions, and my editor wrote a response too. I want to follow up on these things.

Week 3(9th June – 16th June)

Key Accomplishments Last Week

1) Successfully went through the complete presentation on http://forge.mysql.com/wiki/How_to_Build_MySQL_on_Windows/Presentation

2) Successfully built mysql from source by following the instructions http://forge.mysql.com/wiki/MySQL_Internals_Guided_Tour.

3) Resolved all errors that arose from steps 1) and 2) on my system.In the process I gained plenty of insight into the internal working of mysql and ubuntu.

4) Mysqlslap is written in the C API. Hence I began to read about the C API for writing client programs to access the mysql database.

Key Tasks that stalled Last Week

None

…

Week 3(9th June – 16th June)

Key Accomplishments Last Week

1) Successfully went through the complete presentation on http://forge.mysql.com/wiki/How_to_Build_MySQL_on_Windows/Presentation

2) Successfully built mysql from source by following the instructions http://forge.mysql.com/wiki/MySQL_Internals_Guided_Tour.

3) Resolved all errors that arose from steps 1) and 2) on my system.In the process I gained plenty of insight into the internal working of mysql and ubuntu.

4) Mysqlslap is written in the C API. Hence I began to read about the C API for writing client programs to access the mysql database.

Key Tasks that stalled Last Week

None

…

So everybody and their dog hopefully knows about SQL injection attacks these days. Most people should have also heard someone telling them that using prepared statements is the magic super fix to all of these issues. People slightly more in the know will have read that prepared statements lead to all sorts of issues. Some of which can be fixed with hacks (or eventually at the source). Some of which can only be solved of the source also exist of course. Some others can only be fixed with certain assumptions (like using the first set of data for generating the …

One of our replication slave broke last night. This is another strange one. I have multiple slaves running under version 4.1.19 (yup, this is an old one, hehe). But for some strange reason, only one replication slave exhibited the following behavior: It would seem like it cannot create a temporary table while other replication slaves have no problem with it. See below for the example.

mysql> create temporary table abc (id int);
ERROR 1046 (3D000): No database selected

mysql> \u customer
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed

mysql> create temporary table abc (id int);
ERROR 1049 (42000): Unknown database 'customer'

mysql> create table abc (id int);
Query OK, 0 rows affected (0.01 sec)

mysql> \u test
…