2005 LinuxQuestions.org Members Choice AwardsThis forum is for the 2005 LinuxQuestions.org Members Choice Awards.
You can now vote for your favorite products of 2005. This is your chance to be heard! Voting ends March 6th.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
We use DB2 at work... whatever you do don't vote for DB2! I generally spend 10 minutes getting xyz done on MySQL (because it just works) and then spend the next 5 days moving xyz too DB2 because "DB2 is the platform we have always used and we are not about too change now, period".
We use DB2 at work... whatever you do don't vote for DB2! I generally spend 10 minutes getting xyz done on MySQL (because it just works) and then spend the next 5 days moving xyz too DB2 because "DB2 is the platform we have always used and we are not about too change now, period".
Bobby
Yeah, but how much of that time is wasted because MySQL is extremely non-standard? It'd be a much more convincing argument if you were using an ANSI-compliant database as your point of comparison. And you might just discover that you're just thinking about things in ways that databases don't work.
But yeah, DB2 is pretty bad. Only database I've ever seen deadlock on a single row update with no other connections to the database...
Yeah, but how much of that time is wasted because MySQL is extremely non-standard? It'd be a much more convincing argument if you were using an ANSI-compliant database as your point of comparison. And you might just discover that you're just thinking about things in ways that databases don't work.
I agree here!
Quote:
Originally Posted by decibel
But yeah, DB2 is pretty bad. Only database I've ever seen deadlock on a single row update with no other connections to the database...
Well, it shouldn't be possible to make a single row update in an otherwise quiet database deadlock unless you've messed up a bunch of triggers or something (which I hadn't done).
What was happening is that DB2 allows for Serializable and Repeatable Read by locking the 'next row' in all the indexes on the table. If you defined the right combination of indexes... BLAM! deadlock. It was 100% repeatable, too.
The solution was to twiddle some magic parameter that disabled RR and Serial consistency (which was fine in this case since we weren't using them).
Whats this Question? Mysql is the best and the most open one out there. Millions use it and why shouldn't we?
Linux Apache MySql perl/php/python (LAMP) Rocks!!
Whats this Question? Mysql is the best and the most open one out there. Millions use it and why shouldn't we?
Linux Apache MySql perl/php/python (LAMP) Rocks!!
If it was 'the best', then there wouldn't be about 100 gotchas listed at http://sql-info.de/mysql/gotchas.html. It wouldn't think that Feb. 31st was a valid date. It would also come with 'features' such as being able to make a backup without shutting the database down. MySQL's stance is: get the feature in first; worry about it working correctly later. You want to trust your data to that? I certainly don't.
It's absolutely not the most open. The 'free' license is more restrictive than the GPL, which is pretty hard to do. SQLite is the most free: it's public domain. PostgreSQL is close behind; it's BSD license only means you have to maintain the copywrite/license notice and you can't sue UC Berkley.
Millions of people use Windows 98... should you? A lot of people using it doesn't mean it's good, by any stretch of the imagination.
Mysql is the best and the most open one out there.
MySQL now have one of Database pioneers, Jim Starkey, who created Interbase (count Firebird here too) so their future looks bright, but only if they do what Jim says :-)
MySQL is NOT open, with their dual license... Firebird and PostgreSQL are!
MySQL now have one of Database pioneers, Jim Starkey, who created Interbase (count Firebird here too) so their future looks bright, but only if they do what Jim says :-)
That's an if that's unlikely to happen. They've had some clued folks over there for years, yet there's still all kinds of broken-ness.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.