Has MySQL Forked Beyond Repair?

snydeq writes "Fatal Exception's Neil McAllister questions the effect recent developments in the MySQL community will have on MySQL's future in the wake of Oracle's acquisition of Sun. Even before Oracle announced its buyout, there were signs of strain within the MySQL community, with key MySQL employees exiting and forks of the MySQL codebase arising, including Widenius' MariaDB. Now Widenius' Oracle-less Open Database Alliance adds further doubt as to which branch of MySQL will be considered 'official' going forward. 'Forks are a fact of life in the open source community, and arguably an entirely healthy one,' McAllister writes. 'Oracle just better hope it doesn't end up on the wrong side of the fork.' To do so, he suggests Oracle will have to regain the the trust and support of the MySQL community — in other words, 'stop acting like Oracle.'"

Comments

Re:Oracle needs to cater to business not the commu

[growse]

I've heard the arguments that postgres is as easy as MySQL, and they're bullshit.

Lets see:

Postgres has no good GUI applications that can compare with MySQL's

Why you need more than one is beyond me. Isn't Pgadmin enough?

their command line application is just as good in its own way

Well, ok. Whatever 'in its own way' means.

and the market share that ensures you need to google multiple times to find the info you're looking for.

Postgres has some of the best documentation of any open source project I've seen. Sure, MySQL is good as well, but lets not spread bullshit here.

Installing postgres is also a nightmare compared to MySQL.

You mean in a download-the-msi-and-double-click-on-it way, or the apt-get-install-it way?

To sum up: free > $millions, easy > full-featured (in many circumstances).

Well, it's fully-featured, but not necessarily all of those features at the same time. Try doing full-text indexing on a database with foreign-keys on it in MySQL sometime.

Re:MySql

[mcrbids]

PostgreSQL scales well, but is fairly slow on average.

Really? Because any recent review of Postgres shows that it stomps the pants off MySQL in all cases except very simple queries against very small tables. (And really, who gives a !@#% about that scenario?)

Also....

1) It's data validation is excellent.

2) It's extremely stable. In YEARS of working with it, I've had ZERO integrity issues despite managing rather large data sets.

3) Particularly important: it maintains good performance as the query complexity soars. While it can take a bit of tuning, I've done 12 table joins with combined inner, outer, and subqueries and millions of records, with an average return time of around 0.2 seconds. The statement alone was two pages, printed form, on a single-core Athlon 64 with ATAPI drives and 1 GB of RAM.

4) It's FREE FREE FREE!

5) It includes excellent near-realtime replication. (functionally analogous to MySQL replication, which is nice when it works, but since it usually doesn't, well...)

1994 called. It wants its stale information back.