MySQL is getting damn good, especially in 4.x. It still can't do stored procedures which is sometimes a nice feature to have, but it's blazing fast, especially if you're using InnoDB tables (which I recommend).
Supposedly MySQL 5 will have stored procedures, as well as something similar to Oracle's "satellite" feature for across-the-board data replication. MySQL AB also has some huge clients / supporters including Google, HP, NASA and Yahoo! More info on that can be found at: http://www.mysql.com/company/
I personally tend to pick my database type based on a long-term analysis of the project and what language is going to be used to interface with it. I tend to do PHP & MySQL vs. Java & Oracle. PHP & MySQL being the super fast - get things done and make it work well pair, and Java & Oracle being the tank-size work horse to deploy a large-scale high-maintenance, high-access application.
Well, my theory is flawed, I'll admit that. I know of a certain Oracle setup that is "off-line" from 5PM-5AM every day for "maintenance". What good is that for a web-based application? I dunno.
I'm rambling.
~Matt Simpson
On Jul 12, 2004, at 3:02 PM, Karsten Hilbert wrote:
...Personally, I have used MySQL for a number of very large projects; in fact some projects exceed 250,000 users and tables that exceed 4 - 5GB's.Any specific reason you're "hating" on MySQL Karsten?Apparently no other reason than my seeming to be ignorant on MySQL *in critical use*. Thanks for speaking up. After all I would hope they CAN in fact depend on the database they are about to deploy.
Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
