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."
...is a bunch of wimps with no horsepower-ower-ower-ower! Gentleman, start your flames.
"Play is the only way the highest intelligence of humankind can unfold." -- Joseph Chilton Pearce
Please don't dismiss the PostgreSQL "zealots" as trolls, most of their points are truly valid as of the latest released MySQL (4.1) and it's outright embarassing to hear people tell developers using MS SQL Server to migrate to MySQL which is a very common thing to hear here on Slashdot and other technical forums with a Linux/OSS bias.
MySQL 5 is a HUGE leap forward for MySQL and most of the points will probably become moot. Let's just hope they fix the default-value fiasco also...
When MySQL 5 is released PostgreSQL will get some more Open Source competition and that is a good thing.
My other account has a 3-digit UID.
MySQL 5 is a HUGE leap forward for MySQL and most of the points will probably become moot. Let's just hope they fix the default-value fiasco also...
Are they planning on fixing the artistic license that MySQL routinely takes with the data thrown at it? I'm talking about autotruncation, auto "converting" strings to numbers, NULL and 0 being the same thing... Until MySQL takes data consistency or at least validation seriously it will never make it in this shop.
When MySQL 5 is released PostgreSQL will get some more Open Source competition and that is a good thing.
Totally agreed. I'm a fan of Postgres, this is true, but competition is always healthy so long as nobody's playing dirty pool.
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.
I think the real question here is, are all of these features supported under one table type?
MySQL has Fulltext search and relational contraints, but not both at the same time becuase of the different table types.
Unless the MySQL team can get all these features together in MyISAM, don't expect a big uptake.
Don't forget that if you want to distribute it within your organisation, deploy it with your own non GPL application, or even require people to download it to use your non GPL application, you will need to get a commercial license!
The tap is on full, but the water dribbles out
Let me clarify the licensing.
First, if your application is under the GPL or another OSI compliant open source licence, you will not need a commercial licence for MySQL. MySQL AB has issued a "FLOSS Exception" which uniquely makes the GPL licence as used for MySQL compatible with OSI approved open source licences. See our website for more information.
Secondly, if you use GPL software in-house, i.e. you do not distribute, then the reciprocity requirement of the GPL does not kick in so you are free to use MySQL under GPL. (Some call the reciprocity requirement the "viral effect". I call it the reciprocity requirement, or simply the "blessing".)
The two scenarios above cover the vast majority of all cases.
If you distribute a commercially licensed application, then by the same logic that your application is commercially licensed, we think the database should be. This is the Quid pro Quo principle of MySQL AB and of a host of other open source companies.
I hope this info is useful!
Marten Mickos, CEO, MySQL AB
(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.
Or should I just stick with PostgreSQL's "do it yourself" updateable views?
Using Rules/Triggers in PostgreSQL (which I guess is what you refer to with "do it yourself") to implement updatable views is actually much more powerful that "classical" updatable views, as it allows to make all kinds of views (even unions and intersections) updatable - as long as you can write a procedure that updates the involved base tables correctly for your application.
But, yes, MySQL implements updatable views in 5.0.x and for the basic testing I did it works just fine.
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.