Slashdot Mirror

← Back to Stories (view on slashdot.org)

IBM, MS Critique MySQL

Posted by ryuzaki0 on from the some-sqls-are-good dept.

magellan writes "InfoWorld has an article reporting how both IBM and Microsoft are dissing MySQL. While it is understandable from Microsoft, it is interesting that IBM, who often claims to be a defender of Open Source Software, would be so negative. Sun Microsystems and Yahoo are quoted as providing positive opinions on MySQL." On the credit site for MySQL, though, Bingo Foo writes "MySQL has finally answered its detractors who complained about its lack of transactions. A press release today reveals that InnoDB is now fully integrated with the stock MySQL product, allowing ACID-compliant transactions, rollback, and crash recovery. Let the religious wars begin!"

2 of 485 comments (clear)

  1. In other news.... by mwjlewis · · Score: 0, Troll
    In other news. Repeated exposure to the Sun, can cause skin cancer.

    Something Free- is always going to be put down by something that another company can make money off of.

    --
    www.oobersworld.com - For those that ride.
  2. Re:What about SUB-SELECTS? by ajs · · Score: 2, Troll
    Personally, I'd be happiest if MySQL never has sub-selects. When you're forced to work around the lack of sub-selects you are also forced to avoid one of the most costly and difficult-to-optmize features of modern relational databases.

    If they're there in a later release, I'll probably use them, but only because I'm lazy. Views are also one of the worst pigs ever created.

    Now, triggers I'm of two minds about. Simple triggered events (e.g. tbl1.col1 = f(tbl1.col2) where f is a basic, internal MySQL function) should be supported, no doubt about it. But, if what you want is to tie a program to updates, then I think an event model for external applications would be a much better way to go.

    However, if you're not of the "treat the database like hardware" camp that I'm in, you'll be happy to hear this:
    Internally, through a new .frm file format for table definitions, MySQL 4.0 lays the foundation for the new features of MySQL 4.1, such as nested subqueries, stored procedures, and foreign key integrity rules, which form the top of the wish list for many of our customers. Along with those, we will also include simpler additions, such as multi-table UPDATE statements.
    That's from the 4.0 "in a nutshell" page. 4.0 is currently in beta, though if previous MySQL releases are any indicator, don't expect it to be out of beta right away. They're pretty fanatical about stable releases.

    If you start converting now, I imagine you should be in good shape by the time 4.1 is out. Good luck!