Slashdot Mirror
MySQL 5.0.3-beta Released
Zontar The Mindless writes "MySQL Community Edition 5.0.3-beta has been released. This version has support for Stored Procedures, Triggers, Views and many other features, including a number of security enhancements and stability fixes. See the changelog for a complete listing of new features and bugfixes. MySQL 5.0.3-beta is now available in source and binary form for Linux, Solaris, MacOS X, FreeBSD, Windows, and other platforms from dev.mysql.com/downloads/ and mirror sites. RPMs for Red Hat/Fedora and SUSE Linux are also now available for the first time in the 5.0 series. This is the first Beta release in the 5.0 series, in preparation for a MySQL 5.0 production release later this year."
You're almost there. Once your toy database (tm) actually implements those data-integrity things like NOT NULL and DATE correctly, then we can start discussing how it can be used in a real data-critical production environment.
Yeah, right.
Without a calculator, what is 54363 * 23453?
If you said 4, you've done it the MySQL way. As quickly as possible with no regard to giving the correct answer.
Anybody can give the wrong answer quickly. I used to be a MySQL fanboy, then I started hitting the various "Gotchas" that it has where answers didn't come out correctly.
The amount of time cleaning up wasn't worth it. If 95% of their warnings were errors, I probably wouldn't have changed to PostgreSQL.
Things like the below make me nervous:
InnoDB: Commit after every 10,000 copied rows when executing ALTER TABLE, CREATE INDEX, DROP INDEX or OPTIMIZE TABLE. This makes it much faster to recover from an aborted operation.
Rod Taylor
(Intentionally mangled output due to the $%#& lameness filter.)
I'm not disuputing you, and I can't stand lots of mysql's screwy behaviours (I'm a rather big Postgres booster, actually). I'm just wondering how to reproduce it.
-abulafia, currently supporting Postgresql, Oracle, MS SQL Server, Sybase and Mysql.
I forget what 8 was for.
Like, wow! Using a database that has foreign key and !sic! constrains you to actually write numbers to integer fields is sooooo hard to get used to... And that whole "ACID" thingy... spaced out, I tells ya.
-- Sig down
This version has support for Stored Procedures, Triggers, Views and many other features
<asbestos suit>
Those PostgreSQL must be quaking in their boots not that MySQL has reached feature parity with PostgreSQL 6.0. Now that they're only six or seven years behind PGSQL developers will have to keep an eye on them
</asbestos suit>
Anyways I think competition is a good thing, and it's good to see the market leader in the open source database realm become somewhat more industrial strength. I've been puzzled by how more robust, featureful alternatives like PostgreSQL and Firebird are overlooked in favour of MySQL, so at least if it continues to happen MySQL is starting to fit the bill better.
I know it sounds like a slight against MySQL, which really is the best choice in many situations since it is fast, has a smal footprint and is easy to set up, use and maintain. However, MySQL's suitability in web applications has made it so popular that it seems to have pushed alternatives to the sidelines even when they are the better choice. For example, I think I'd much rather set up an accounting system with a PGSQL backend over MySQL.
In any case, I encourage people to look at ALL the alternatives. PGSQL 8.0 is out and is very impressive. Also, devlopment of Firebird 2.0 is underway so expect rapid improvements as this major release gets closer to completion.
Coming off a project with a MS SQL Server 2000 backend I'd have to say the more alternatives the merrier. MSSQL2K is pretty stale and after workig with PGSQL for so long it makes MS SQL look completely brain dead in almost every way--particularly in the areas of concurrency and locking. It'll be interesting to see how Yukon stacks up, but at least MySQL and the others will provide some serious competition.
A CEO that reads slashdot?! :-)
Where do I apply?