4 ms·
Even if and when Oracle kills MySQL, there's already a fork of it as of version 6.0 called Drizzle. More background information of this can be found at http://
by kungfudoi 17y ago
Even if and when Oracle kills MySQL, there's already a fork of it as of version 6.0 called Drizzle. More background information of this can be found at http://en.wikipedia.org/wiki/Drizzle_%28database_server%29 http://en.wikipedia.org/wiki/Drizzle_%28database_server%29.
Official homepage: http://drizzle.org http://drizzle.org
Blog: http://blog.drizzle.org http://blog.drizzle.org
Source code: https://launchpad.net/drizzle https://launchpad.net/drizzle
- edmccaffrey 17y agoDrizzle is not a valid choice for apps that require things like stored procs and triggers, which they removed. Of course, not every app requires what they remove; MariaDB is a fork by the core MySQL team, if those features are needed and MySQL cannot be used.
- bensummers 17y agoThey're planning to add "server side scripting" in any language to replace stored procedures. It sounds quite cool. http://krow.livejournal.com/638941.html http://krow.livejournal.com/638941.html I have been writing extensions to Postgresql in C++ recently, and it's amazing what you can do if you have the full flexibility of loading a .so into the db process and doing whatever you want.
- edmccaffrey 17y agoI didn't mean to imply that it is no longer a useful or interesting piece of software; just that it is not a simple migration for some project that specifically use MySQL features. I did the same thing in SQL Server, too, so it's not a new concept and the other RDBMs with that ability still have a use for traditional stored procs. My experience with both stored procs and running actual programming languages on the database is that one does not replace the other; but I'll wait with an open mind to see.