Until lately, I have used MySQL for those my database needs in most my server projects.

However, after Oracle arrived and bought MySQL, there appears to become some uncertainty about the way forward for MySQL.

So I am left wondering whether I ought to stay with MySQL (which I am fairly acquainted with), or must i change to something similar to PostgreSQL. Any ideas?

MySQL and PostgreSQL are generally open-source DBMSs that will still be produced by independent parties should their current maintainers (corporate or else) become bored. MySQL already has some interesting forks for example Drizzle which might rise to more prominence if Oracle decide to allow the original project stagnate (well, a lot more than Sun did...).

You need to choose according to your projects' technical needs instead of nebulous arguments that certain or even the other will ‘win’.

(Personally I certainly think it's wise to possess knowledge about both.)

If you are searching for grounds to change to postgres, "Sunoracle bought MySQL" is not a high quality one. MySQL will probably be around for some time.

From Oracle Makes Obligations to ... Customers of MySQL:

 4.Resolve for enhance MySQL later on underneath the GPL. Oracle shall still enhance MySQL making subsequent versions of MySQL, including Version 6, available underneath the GPL. Oracle won't release any new, enhanced version of MySQL Enterprise Edition without contemporaneously delivering a brand new, also enhanced version of MySQL Community Edition licensed underneath the GPL. Oracle shall keep the origin code of versions of MySQL Community Edition openly available at no cost.


 6. Increase investing on MySQL research and development. Oracle commits to offer appropriate funding for that MySQL ongoing development (GPL version and commercial version). Throughout each one of the next 3 years, Oracle will expend more about research and development (R&D) for that MySQL Global Business Unit than Sun put in its newest fiscal year (USD 24 million) preceding the closing from the transaction.

Despite that, remember, it's GPL. If Oracle does something really dumb, the worst-situation scenario is really a fork.

MySQL had been in danger before Oracle bought SUN, growth and development of version 6. was canceled, much like version 5.4.

Version 5.1 is supported before the finish of the year, 2010-12-31, next, only extended support can be obtained, but you spend for this. Forget about community patches. Version 5.5 or 5.6 continue to be not GA, still alpha and/or beta. If you're able to do without patches, go on, if want patches try not to want the balance, move onto another database.

MariaDB (Monty's cool product) is applying the MySQL-code, his last patches came several weeks after MySQL launched it's patches. MariaDB does not look too good, it really wants to stay not far from the initial and it has it's dependencies. MariaDB may be in danger the coming year for it's support on 5.1 versions.

And all sorts of these complaints began before Oracle got involved. A lot of reasons to escape from MySQL, but (imho) Oracle is't the primary problem. Oracle wants money as well as their clients are likely to pay, that's been very obvious from the beginning.

An identical factor happened with Sybase also it appeared just like a fairly smooth transition. Obviously that's different situation, but they're similar...

For which it's worth Oracle claims MySQL is going to be around for some time in the future...