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 [...]

This is just a quick start for a brainstorming of what we all hate in todays CMS (I am including portal/community software here as well and I guess most also applies to web shops) software out there. I have written a very small CMS application myself ages ago so I do not have experience in what its really like writing and maintaining a big one. All I know is that its insanely painful to deal with any of them, though if your site is all about having admins managing tons of static content or end users wanting to interact, there is little way around these ugly beasts. I guess it all boils down to how to persist changes made through and admin panel. Somewhat related is the issue of scalability which to me mainly boils down to how easily can the storage logic be changed without changing the business logic on top.

The biggest gripe that results from these ever so powerful admin panels is the tendency to have these settings stored in the …

So Monty now claims that Oracle is MySQL's main competitor. Given that for years MySQL AB has said the exact opposite is kinda odd. They did have a short run in with SAP but that didn't go any where .. well it resulted in MySQL loosing focus, adding tons of barely functioning features which ended up in this entire roadmap debacle we are still suffering through. Anyways the EC has thrown in their hat to stop the deal. Björn seems to share their concerns and so do many others it seems. I still don't get it. This is my attempt at clarifying my point of view and also making sure that people remember the proper terminology (stop using commercial and proprietary as synonyms).

First this all revolves around the assumption that Oracle lets MySQL linger.

Secondly, anyone can provide commercial support …