I'm moving out of MySQL
Submitted by develCuy on Fri, 2008-05-23 17:21
This was a postponed decision, because I did not liked to listen to an experienced counselor.
Sun Microsystems is in the way of closing MySQL, which is a "feeling" years ago, but has never crossed the red line of "minor risk". Unfortunately this is a sad reality today. The good news is that FLOSS is an open space for alternatives in most of cases.
So where am I going now? I'm going back to PostgreSQL, although is rigid but that guarantees will be that way for preserving the FLOSS philosophy.
This doesn't means that I'm not going to work with MySQL anymore, but just a change of priorities and preferences. Take by example that now I'm in the process of moving to PostgreSQL everything at home, and will recommend the alternative for upcoming projects.
Not that bad at all... right?
Blessings!
I don't feel they closed anything
Some time have passed and I don't feel they (Sun) closed anything.
And moving to a different database is something not really an option, if software only supports MySQL...
Hopefully, this will influence PG support in Drupal...
I hope this will also indirectly improve PG support in Drupal. Most modules still have problems with PostgreSQL. Be it just because it's not been tested, or not documented enough, in the end you end up with modules (even the system module) that say they work with PGSQL 7.3 while they only effectively work with 8.x. It's a bit of a mess, really....
Post new comment