Hi!

On August12th, we will host a live webinar which introduces MySQL products. Here is general information:

• Title: Introducting MySQL Products

• Date: Tuesday, August 12 at 2:00 pm JPT,at 3:00 pm in Sydney, at 1:00 pm in Singapore, Beijing and Manila Philippine, at 2:00 pm in Seoul, at 10:30 am in Mumbai (the presentation will be approximately 45 minutes long followed by Q&A)

• Presenter: Ryusuke Kajiyama,MySQL Senior Technical Evangelist

• Registration URL: http://www.mysql.com/news-and-events/web-seminars/display-183.html

Join us for this informative webinar which will deliver a comprehensive introduction of MySQL products and services such as MySQL Enterprise,  MySQL Cluster, MySQL Embedded, consulting service, along with examples of …

Today marks a big day in the history of the Malaysian Government - they’ve released their first fully open source software package, MyMeeting.

Poking around their Trac installation, they use PHP and MySQL 5 (5.0.51a from Ubuntu, even!). Of course their install documentation suggests a lot of Windows usage, but this is a step in the right direction.

Give it a twirl. Report bugs. How many more governments out there are writing and releasing open source software packages? Or is this a first?

Thanks to Glynn for pointing me to the right thread on opensolaris.org (in a comment on my Good adventures with OpenSolaris post). The package verification thingy (pkg verify -v -f SUNWfirefox) did actually throw an error (indicating some sort of problem). So that’s pretty neat. The fact that it got into trouble in the first place isn’t good, but corruption detection is the next best thing.

I still occationally hit the bug in VirtualBox where if you have 127.0.0.1 in your resolv.conf on your host (e.g. running a local caching nameserver), VirtualBox passes this through to the guest, so the guest tries to use the guest 127.0.0.1 as a nameserver - this usually doesn’t work so well.

The good news is, Firefox now works in my OpenSolaris VM.

The bad news is that even though I’ve gone and …

This post is SEO bait for people trying to scale MySQL’s write capacity by writing to both servers in master-master replication. The short answer: you can’t do it. It’s impossible. I keep hearing this line of reasoning: “if I make a MySQL replication ‘cluster’ and move half the writes to machine A and half of them to machine B, I can increase my overall write capacity.” It’s a fallacy. All writes are repeated on both machines: the writes you do on machine A are repeated via replication on machine B, and vice versa.

With all the news about the fork to MySQL to the new lean-mean drizzling machine, I might have been the only one that actually didn't really like the idea.
Taking out views, triggers, stored procedures, events and everything else since MySQL 4.1 didn't really appeal to me. But this coming from the guy that wrote "Using Business Rules in MySQL" and "Useful Ways to use Views", can you really blame me?


I not happy, but they are probably right
Well, it seems to me like its going backwards. Albeit I completely understand that its for the purpose of going forwards.

Take out the stuff that the vast majority of MySQL users don't use - mainly web site developers - and make it very fast and …

As you may know mysql fulltext search is not highly scalable.  One of the options to get around this scalability limitation, which I prefer, is to use Sphinx.  You can use Sphinx with out having to alter your mysql installation.  But, if you would like to use from within mysql and not have to worry about how to pass data between Sphinx and MySQL, you can enable sphinxse (sphinx storage engine).  It is not included with mysql by default so you will have to compile it yourself.

Here are the instructions on how to get sphinxse compiled with your mysql installation on CentOS x64.  I am sure same instructions will work for other flavors but I have not tested it.  I will be compiling the most current version of sphinx (0.9.8) with most current stable version of mysql (5.0.51b) at the time of the writing.  Let’s get the appropriate …

Today, the root file system on our public svn server nearly ran out of disk space. The reason? The /tmp directory was quickly filling up with temporary files created by websvn, which I set up parallel to the FishEye repository browser for testing purposes. A quick investigation of the apache log files revealed the culprit - a crawler from Microsoft was running haywire and decided to ignore the rules in the robots.txt file, even though it did actually looked at the file before!

Here is how robots.txt looked like (I now changed it to disallow everything):

User-agent: *
Disallow: /fisheye/
Disallow: /websvn/

If I am not mistaken, no crawler should actually consider going into the SVN browser directories. Some snippets from the apache log:

Keith Murphy asks if you have ever edited your dump files before feeding them to the database. And he recommends using sed. This reminds me of a war story, when I was consulting in Milan. The customer needed, among other things, to import a huge text file (created by a third party application) into a MySQL database. I did everything, including a cron job to load the data every day. By the time I left for the airport, the third party application hadn't yet provided its first sample, but since we knew the fields list, it was a simple case of creating a LOAD DATA INFILE command.
I was boarding my plane, when the customer called, saying that the application was giving dates in the wrong format. Instead of 'YYYY-MM-DD', it was using the Italian human readable format 'DD/MM/YYYY'. No Internet was available, and with just a few minutes …

A new MySQL product is born. The preview release of MySQL Connector/C++ is available for download at http://downloads.mysql.com/forge/connector_cpp_preview . Connector/C++ is a new database driver to connect C++ applications to the MySQL Server. The preview mimics parts of the JDBC 3.0 API and is licensed under the terms of the GPL (plus FLOSS License Exception). Have a look at the announcement and the MySQL Connector/C++ wiki page for further “official” …

A new MySQL product is born. The preview release of MySQL Connector/C++ is available for download at http://downloads.mysql.com/forge/connector_cpp_preview . Connector/C++ is a new database driver to connect C++ applications to the MySQL Server. The preview mimics parts of the JDBC 3.0 API and is licensed under the terms of the GPL (plus FLOSS License Exception). Have a look at the announcement and the MySQL Connector/C++ wiki page for further “official” …