IBM, MS Critique MySQL

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!"

Comments

MySQL is still a toy

[dutky]

Now that they've fixed the lack of transactions (twice. What was wrong with the first time?) they can implement subselects and relational integrity. When they have all three implemented, I'll think about replacing PostgreSQL.

(P.S. Does MySQL have any support for checkpointing and hot backup, or do I have to take the whole database down during maintainance?)

Informix?

[Squeezer]

Don't forget that IBM recently bought out Informix and now sells InformixSQL as well as DB2.

Re:What about SUB-SELECTS?

[bovinewasteproduct]

It would be nice if PostGres would support altering live tables (add/remove/modify columns), and stored procedures.

Have you checked out 7.3 for the column support? As for stored procedures, it has support for this also.

BWP

Re:Of Joins and Sub-Selects...

[rtaylor]

Well.. Some databases don't lock rows or tables (unless necessary). MVCC is a superior option (Oracle / Postgresql for implementation references).

Anyway, there are a number of things that subselects can accomplish that joins cannot do as easily. Not the best example below, as it could be done in other ways and the formatting isn't so great, but anyway:

SELECT col1, max, othercol
FROM table
JOIN (SELECT max(col3) as max
, col1
FROM table3
GROUP BY col1) as ttab
USING (col1)
WHERE 2 = (select count(*)
from table2
WHERE table.col1 = table2.col1);