Being an employee of MySQL (past and present), every time I see something related to dolphins it catches my eye - and I just came across this:

Scientists say dolphins should be treated as ‘non-human persons’

The treatment of dolphins has long been an issue for me, I utterly despise some of the things I have seen, and read about. MySQL’s dolphin - Sakila - has always been seen as a symbol of freedom. This is marred by reality, hopefully this will change:

“The researchers argue that their work shows it is morally unacceptable to keep such intelligent animals in amusement parks or to kill them for food or by accident when fishing. Some 300,000 whales, dolphins and porpoises die in this way each year.”

Some other things in the article also ring true for me, in other ways. …

If there’s one thing that will always make me angry, it’s people that should not be editing my code going and editing my code. If you want to change something on the server and you have sudo privileges please let the real admin know beforehand. I don’t mind people improving processes or scripts but if [...]

And I looked back and thought of updating this post… Recently Monty has posted again and I completely convinced with whatever Monty has conveyed now or earlier. The explainations he has provided under self-interview,…

The post Petition – Help saving MySQL – II first appeared on Change Is Inevitable.

Like I mentioned in my last blog post, we have a company internal framework that is quite advanced thanks to the various symfony components we have integrated. Its other main advantage is that it can do a lot with very little code. The net benefit of this is that it's extremely easy to learn and debug. Especially the last point can be somewhat painful with symfony since inheritance trees tend to be quite large and things get delegated to other objects etc. However once you start getting a hang of where things are, symfony is very powerful indeed. The other day we had a little hackday at Liip where we wanted to write a little google maps app. The idea was to have different kinds of markers shown on the map which when clicking on them would both load some data into the classic GMap marker bubbles as well as some additional data into a div …

Recently MySQL has offered MySQL Certification Free Retake on both DBA or Developer Certifications for a limited time. For MySQL Certifications: 1. MySQL 5.0 Data Base Administrator Certification (SCMDBA) –…

The post MySQL Certification Free Retake: Get TWO chances to get MySQL Certified first appeared on Change Is Inevitable.

And I looked back and thought of updating this post… We all are aware about the acquisition happened to MySQL; Sun and now Oracle. A common understanding tells me that…

The post Monty: Help Saving MySQL – The Oracle & EC first appeared on Change Is Inevitable.

What on earth is Monty (and Richard) thinking? How can you spin around 180 and expect to come of believable? How can suddenly the GPL be the wrong choice? How can suddenly OSS depend on proprietary sales? Anyways, even without this change of minds, I do not believe in their arguments. I also do not hold stock in any of the involved companies (well I do not hold any direct stock in any company only indirectly by way of a few retirement funds I hold), so why do I keep posting on this? The reason is that I think this kind of stuff hurts OSS. It creates the kind of FUD we were worried about Microsoft spreading about OSS. Now that they are shutting up more and more, some seem to feel a void that they need to fill with some FUD of their own. To me Monty is just abusing the lack of understanding but the growing interest from the EU commission about open source to get his baby back on the cheap, or at least as much control as he can, since after all his baby …

Drizzle originally inherited the FRM file from MySQL (which inherited it from UNIREG). The FRM file stores metadata about a table; what columns it has, what type those columns are, what indexes, any default values, comments etc are all stored in the FRM. In the days of MyISAM, this worked relatively well. The row data was stored in table.MYD, indexes on top of it in table.MYI and information about the format of the row was
in table.FRM. Since MyISAM itself wasn’t crash safe, it didn’t really matter if creating/deleting the FRM file along with the table was either.

As more sophisticated engines were introduced (e.g. InnoDB) that had their own data dictionary, there started to be more of a problem. There were now two places storing information about a table: the FRM file and the data dictionary specific to the engine. Even if the data dictionary of the storage engine was crash safe, the FRM file was not plugged into that, so you …

Just got the following in my email this morning. I sure wish they had done this earlier. “Free Inbound Data Transfer (until June 30, 2010) Data Transfer into AWS will be free of charge from now through June 30, 2010, making it even easier for customers to get their data into AWS. This applies to [...]

This is a follow up on a previous post about Amazon’s EC2 cloud services. You may recall that I had the Kontrollbase demo server hosted there until I was hit with a >$370 bill for less than 2 weeks of service. Now, you may think you want to say “hey you should have known the [...]