Slashdot Mirror
MySQL AB Calls v4.1.7 Production Ready
puppetman writes "MySQL announced a few hours ago that 4.1 has been deemed production ready with the release of 4.1.7.
The major enhancements of 4.1 include sub-selects, faster communication between client and server (thanks to parameter binding), replication over SSL, and lots more. A full list can be found here.
Time to rehash those tired arguments about why MySQL is not a real database, and (Postgres/Oracle/SQL Server/Access/SAPDB/Ingres/etc) is the only real database out there."
Does the "production readiness" include ACID?
Sincerely,
Pan Tarhei Hosé, PhD.
"Homo sum et cogito ergo odi profanum vulgus et libido."
MySQL is fine for load/store operations or other places where complex operations on set are not required. MySQL is not suitable for complex queries.
MySQL is a bit like Windows 98 vs. a multi-user OS with virtual memory. Most people just need a single user computer that holds their email and lets them play games.
However, for those who need the features a multi-user OS they cannot simply hack on those features to Windows 98.
It isn't that MySQL isn't a real database it is just that its feature set severely restricts the tasks it is able to do well.
Yes, you COULD build a bank on MySQL just like Diebold makes Windows 98 based ATM machines.
Whether it is a better idea to simply build your bank on Postgresql or Oracle and pay higher machine / licensing costs is an excersize for the reader.
There are spots where Win98 and MySQL are well suited however, there are a lot of cases where it is completely out classed by other products.
Myself, I'd much rather not use all the features of Postgresql and have them available later than build on Mysql and if I need the feature have to port the application. If I run up against performance limitations of Postgresql I simply buy better hardware.
Not everyones SQL usage is limited to "SELECT * from comments were story_id = 23456"
Hardware is almost always cheaper than a programmer's time.
Ok, I'll bite. Why is the Databases icon a wheelbarrow?
Others say my-sequel
Is there a correct answer? I see it in print 1000 times more often then use it verbally, so I don't have a good base to judge from.
A Multiplayer Strategy Game for Mac OS X, Windows, and Linux
Does MySQL still silently substitute its best guess when you try and insert an invalid value into a column?
Does MySQL still silently substitute a non-ACID table type when you ask for an ACID table type and it isn't available?
Does MySQL still silently alter the data you insert into varchar columns by stripping trailing spaces?
MySQL used to be riddled with all kinds of behaviours that the MySQL developers thought might be handy in some circumstances, but that silently alter or ignore the programmer's/DBA's instructions and the SQL specifications. Have the developers gained enough of a clue to fix these (intentional, documented) problems?
The official way to pronounce ``MySQL'' is ``My Ess Que Ell'' (not ``my sequel''), but we don't mind if you pronounce it as ``my sequel'' or in some other localized way.
and all you socialist that think everything should be free can't complain about it either!
- Schemas
- Views
- Rules
- Check constraints
- Domains
- Triggers
- Custom datatypes
- Stored procedures in no less than five different programming languages
- Geometric/spatial datatypes and indexes
- Real type safety
- Errors when the alternative is data corruption
- No silent failures
- Enforcing a difference between NOT NULL and DEFAULT directives
- Consistent foreign key enforcement (Target table must also be InnoDB, ON UPDATE does not allow recursive updates on the same table, out of range violations, brain dead implementation of NO ACTION)
- Better transition to Oracle (closer feature parity)
- Substandard transaction support (The time required to roll back a transaction increases in proportion with the number of operations performed during that transaction; Any non-InnoDB tables referenced in the transaction will not rollback)
And have they fixed the bug where CREATE INDEX, DROP INDEX, and most ALTER TABLEs rebuild the whole InnoDB table? It's been a year.And how about bugs like this (http://bugs.mysql.com/bug.php?id=5670) where creating an index destroys the table. Nice.
- I don't need to go outside, my CRT tan'll do me just fine.
Forgot cursors. Silly me. And no, support in alpha code doesn't count. Until it can be put on a production server, it's a wishlist item, not a feature.
- I don't need to go outside, my CRT tan'll do me just fine.
Does mysql still by default install and run "network enabled" with default admin passwords set?
:)
,
Someone at work tried it once and they got hacked in one day
Love
Zaq
Now that MySQL users now talk about how much they enjoy their subselects, a feature which only a couple of years ago was being derided as just extra bloat, how long until 5.0 goes stable?
On that day, the hordes of MySQL developers will raise a chorus singing the praises of their new stored procedures, views and cursors. And behold! They didn't even slow down the product. Blessed be the MySQL programmers!
Until that day however, stored procedures are "useless" and "needlessly complex." The same with views and cursors. They only serve to slow things down. Of course those pesky naysayers of MySQL will point out that those features have been in PostgreSQL and Firebird for years. But no! Our golden calf does not yet support them in production and until it does they are obviously useless bloat.
Do you like it? I call this piece "Ode to a MySQL Fanboy."
- I don't need to go outside, my CRT tan'll do me just fine.
There are a few Databases I would look at for a client.
Oracle...
DB2...
Now DB2 would be if they were already using DB2.
Not that Oracle is better, or that I trust them, but in computing if there are 100,000 other customers using it, you cannot be sure it will stand up for your usage.
So size does matter. [for databases, and male gentalia (sorry folks)]
I am not a database admin. I personally like MySQL and use it for my own development. I hate getting confused between the oracle way and the mysql way.
#hostfile 0.0.0.0 primidi.com 0.0.0.0 www.primidi.com 0.0.0.0 radio.weblogs.com
I'm using MySQL-3.23.58 (it's alive!)
I could use MySQL-4.0.21 (it's alive!)
I don't like use MySQL-4.1.7 (it's dead forever!)
I don't must use MySQL-5.0.1 (it's dead forever!)
open4free ©
...and figure out which ones are being run most frequently with PQA. Works with PostgreSQL, too!
The Army reading list
I'm not sure what the other distros do. I do remember that the mysql install doc tells you to change your root password.
Or maybe your "coworker" did not read the docs?
"Avoid employing unlucky people - throw half of the pile of CVs in the bin without reading them." -- David Brent
Thank you for making these sensible points.
I really think way too much time is spent on bagging other people's choices.
Why would we want to give proprietary vendors ammo like "the open source world is divided"... why not spend time on promoting the various open source solutions in general, and presenting the diversity and choice that it offers as the good thing that it is?
Obviously not all databases are the same, in feature set, cost, etc.
Everybody would hate if that was the case.
WTF is then this childish "my dad has a bigger dick" competition in the postings?
The installer does not work 100% of the time. It took two tries to get it to install completely and then finally after that it didn't work with PHPMyAdmin (though obviously not the fault of MySQL), I gave up and went back to 4.0 (Note: I am a database admin, but the people that will use it afterwards are not, so they cannot use the command line).