MySQL Readies Release Candidate For 5.1

Anonymous Dolphin writes "MySQL has released plans for a final RC for the MySQL 5.1 server. Monty Widenius, the CTO and founder of MySQL, has put up a request for more feedback from the community. You can get the latest RC here. Please help with the testing of 5.1 and report your bugs here."

Comments

nice feature set

[RelliK]

Traditionally, that is to say, up until MySQL 5.1.22, InnoDB handled newly inserted records into an InnoDB table with an AUTO_INCREMENT column by using a global counter which held the last value for the auto-incrementing column. A lock would be placed on this counter for the duration of the SQL statement which did the inserting...
The new server variable, innodb_autoinc_lock_mode controls how InnoDB treats statements which insert rows into an InnoDB table with an AUTO_INCREMENT column. Depending on your environment â" specifically, whether you are using the binlog for replication or recovery purposes and whether you are executing "batched insert" statementsâ" you can set this variable to 0, 1, or 2. 0 corresponds to the traditional mode, and is not recommended except for very specific scenarios (see the doc link above). 1 represents "consecutive mode" and is the default. In this mode, only statements where InnoDB cannot determine the number of rows to be inserted will use the global auto-increment lock. All other "simple insert" statements (even those inserting multiple records in batch mode) will use a faster, lighter locking mechanism, which results in significant scalability increases. The final setting, 2, represents an "interleaved" mode and has even greater scalability improvements, but cannot be used in scenarios where the binary log is being used for recovery or statement-based replication.

So now mysql can handle two concurrent inserts? Nice! Except for the fact that this new amazing option is incompatible with replication. MySQL is going to become a real database. Any time now...

Re:Do people trust this project anymore?

[GooberToo]

Your response was condescending and presumptive.

Your response is paranoid and childish. Sometimes you have to hear things you don't want to hear. The AC's response is actually funny and accurate. By in large, most MySQL users are children when it comes to relational databases. You don't have to be a PostgreSQL zealot to recognize that fact. Simple fact is, MySQL is the low rung on the SQL ladder. All DBAs worth respecting understand this simple fact. In other words, what you assume to be zealotry can just as likely be a factual statement by a knowledgeable person.

Just because you heard something you didn't want to hear doesn't mean it was delivered by a zealot. The fact that you're so easily confused by such a fact is a significant indicator the AC's comment was correctly targeted (you're too close) at you. Your response also implies you are in fact a MySQL zealot. Otherwise, why so easily offended by a comment which was obviously presented with levity, by an AC, in a trollish manner. Getting upset about that is just plain silly.

At the end of the day, with so many excellent relational databases available at zero or little cost, choosing MySQL as your database speaks poorly of you. Just about any database is better than MySQL. Imagine a friend bringing home a cheap Chinese made, Yamaha reproduction and declaring they are tired of "zealots" pointing out that better bikes exist. Well, your friend might be tired of hearing it, but it doesn't change the facts. It doesn't take a zealot to point out that bike is a complete PoS; and without regard to zealotry, better options exist. At least with a bike, you can defend such a purchase from a cost perspective. No such hand hold exists when it comes to the field of freely available databases; almost all of which are better than MySQL.

Lastly, please don't forget that one need only be knowledgeable about relational databases to dislike MySQL. Zealotry need not be a factor.

Re:Do people trust this project anymore?

[gravyface]

At the end of the day, with so many excellent relational databases available at zero or little cost, choosing MySQL as your database speaks poorly of you. Just about any database is better than MySQL.

That's a bit harsh and unrealistic.

In Real Life (tm), you don't always have that choice: sometimes you take what's given to you and roll with it, sometimes you have to use what you know best to get the job done.

I use both nowadays: I do feel more comfortable with MySQL (mainly the tools, auth. mechanisms) because for many years, it was the only option available: host didn't provide Postgres support, xyz application didn't support it, or I personally couldn't justify the risk/learning curve for a tight project.

Postgres may be "superior" to MySQL, but that doesn't mean it's the right choice all the time.