Many systems are already in production when we get asked to take
a look or, interestingly, a few weeks before deployment. The
latter is not optimal, but it's still better than not contacting
us until something goes wrong. At Open Query we like to focus on
problem prevention and skills transfer. This saves so many
hassles and thus over time saves money for the client =
win.
The reasons for asking for external input late(r) are diverse,
and generally not even technical or financial. But we all know
the saying "prevention is better than a cure" and that
has benefits for a company's bottom line; potentially even its
future. Particularly in the current economic climate, such
advantages are gold.
Another other important aspect is scope. MySQL operates in a
larger architecture; we can look at the server and improve the
configuration there, but if queries are just wrong, they need to
be fixed in the application. …
I never do memes. Especially not publicly. But, hell, I was tagged by Brian Moon and he's cool enough to
warrant some effort. Lots of folks in the MySQL / etc communities
were bit by this one. So I'll give it a (late) go :)
Enter useless factoids!
1. My real name isn't dormando! Okay hah hah maybe obviously.
While I'm not nearly as hardcore as chromatic or
MenTaLguY
I am one of those weird people who uses a nickname too much.
Sorry folks, it doesn't mean anything, I made it up when I was
8.
2. I grew up in Massachusetts, worked in New York City for a few
years, and now reside in California. I find the lack of seasons
refreshing, but a little maddening. For a while I was traveling
cross-country every few …
My O’Reilly webcast is now online at youtube. Comments welcome!
The problem with broken group commit was discusses many times,
bug report was reported 3.5 years ago and
still not fixed in MySQL 5.0/5.1 (and most likely will not
be in MySQL 5.1). Although the rough truth is this bug is
very hard (if possible) to fix properly. In short words if you
enable replication (log-bin) on server without BBU (battery
backup unit) your InnoDB write performance in concurrent load
drops down significantly.
We wrote also about it before, see "Group commit and real fsync" and "Group commit and XA".
The problem is the InnoDB tries to keep the same order of transactions in binary logs and in transaction logs and acquires mutex to …
[Read more]In just over 2 weeks I’ll be the invited speaker in Washington DC to Best practices for migrating applications to MySQL. This workshop is being held in conjunction with Carahsoft and Sun/MySQL and aims to provide to the Federal sector valuable information for the continued usage and uptake of Open Source and specifically MySQL.
As part of my preparation I’m happy to hear from any organizations that have successfully migrated from Oracle/SQL Server/Informix/Sybase etc to MySQL and would like to be cited.
While I have been involved in the process I am also happy to hear of reasons why a migration failed, was aborted or postponed. This is all valuable information in determining what are the most ideal applications.
I just wanted to send out a quick update. I have not been able to blog as much as I would like in the last seven or eight months. There is a good reason. Sheeri Cabral and I have been writing a book to be released by Wiley publishing in May of this year. And, finally, we are pretty much done with it. Yeah!!
So, I will have some more time to blog. A lot of changes coming down the road so stay tuned!
|
MySQL Conference and Expo is coming up to Santa Clara this April. The program schedule is really easy to navigate and tells you about everything there's to partake of.
A quick review will show you that the quality of the
no-nonsense presentations will be amazing, and it will be a
true privilege to attend the conference. (We should thank
the MySQL community team for helping ensure this high level
of technical quality and relevance.) |
The Facebook juggernaut is an interesting environment for
application developers. It is well documented for the most part
and supports all the popular development languages. So I created
a quick app to help promote MySQL certification and gave it the
name MySQLQuiz.
The first step in app development is at the bottom of every
Facebook page. That is where you will find the 'Developers' link.
The documentation here is very good and you will be be able to
quickly obtain the application's API Key and the applications
'secret'. Each app is going to have unique values for
these.
The examples I will give are in PHP and using the supplied PHP
library. I was able to get all this running on a test
server.
The bare bones was
[Read more]
<?php
require_once 'facebook.php';
$appapikey = "yourappapikeyhere";
$appsecret = "yourappsecrethere";
$facebook = new Facebook($appapikey, …