Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Databases Programming Software IT

MySQL Readies Release Candidate For 5.1 168

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."
This discussion has been archived. No new comments can be posted.

MySQL Readies Release Candidate For 5.1

Comments Filter:
  • nice feature set (Score:5, Insightful)

    by RelliK ( 4466 ) on Wednesday July 16, 2008 @09:04PM (#24222255)

    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...

  • by Anonymous Coward on Wednesday July 16, 2008 @10:36PM (#24223055)

    Does anyone know of anyone whom MySQL has forced to pay them for their database?

  • by Majik Sheff ( 930627 ) on Wednesday July 16, 2008 @11:53PM (#24223687) Journal

    Your response was condescending and presumptive. I never said I favored MySQL or any other DBMS for that matter. Your snotty little comment about playing in the street only reinforces my already negative view of Postgres zealots.

    It doesn't matter how right you are about whatever it is. Like it or not, how you deliver your message is as important or more important than the message itself. This applies to just about anything: databases, operating systems, which end of a softboiled egg you eat first, and of course, politics.

    You zealots have a lot in common with Ron Paul supporters. Any merit your cause might carry is completely nullified by the overwhelming nature of your enthusiasm.

    I'm done now. I will never comment on this subject again, mainly because I'm tired of burning karma on ACs, but also because I know that nothing I say matters to anyone on either side.

  • Re:Triggers (Score:4, Insightful)

    by gbjbaanb ( 229885 ) on Thursday July 17, 2008 @07:57AM (#24226181)

    In life, you have choices:

    a. get what you're given
    b. get what you pay for.

    choose one, and never complain because you can't mix and match.

  • by GooberToo ( 74388 ) on Thursday July 17, 2008 @08:36AM (#24226529)

    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.

  • by gravyface ( 592485 ) on Thursday July 17, 2008 @09:45AM (#24227235)

    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.

  • I'd love some proof on that 'children' comment. MySQL is a low rung in price, but there are much lower rungs to be had -- SQLite comes to mind even.

    The fact that MySQL is easy to configure and easy to use should not be used against it -- and it is for those reasons that so many people with very little SQL skill have been introduced to a SQL server. Had Postgres' developers made it half as easy to install and manage on my machines 10 years ago, many people would now be using it instead.

    As it stands today, MySQL is an excellent platform for relational database development. It has limitations, and there are better products, but not everyone is writing (for a random example) VISA's payment processing system.

    Your bigotry is apparent, and its just bigotry.

If God had not given us sticky tape, it would have been necessary to invent it.

Working...