| |||||||||||||
A look at the MySQL forksA look at the MySQL forksPosted Apr 23, 2009 1:18 UTC (Thu) by sbergman27 (guest, #10767)Parent article: A look at the MySQL forks
"""
In light of this uncertainty, the discussion soon shifted to the trickier question of what branch constitutes the MySQL. The project has been forked multiple times several even in the past year. Considering that each competitor is led by a heavyweight MySQL developer and has its own goals, how is a humble database administrator supposed to choose? """
Errr... maybe choose PostgreSQL, which doesn't have these fragmentation issues?
(Log in to post comments)
A look at the MySQL forks Posted Apr 23, 2009 8:13 UTC (Thu) by rahulsundaram (subscriber, #21946) [Link]
There are PostgreSQL forks however. EnterpriseDB is a fairly popular proprietary fork.
A look at the MySQL forks Posted Apr 23, 2009 15:08 UTC (Thu) by sbergman27 (guest, #10767) [Link]
However, I don't recall there ever being any question as to the *real* PostgreSQL code base. And be careful with the "p" word; I'm sure you are familiar with MySQL's history.
A look at the MySQL forks Posted Apr 23, 2009 16:04 UTC (Thu) by rahulsundaram (subscriber, #21946) [Link]
"Real" MySQL is whatever is at mysql.com. I don't see why I should be careful about calling a proprietary fork, one. That has nothing to do with MySQL's history. What are you referring to anyway?
A look at the MySQL forks Posted Apr 23, 2009 23:56 UTC (Thu) by sbergman27 (guest, #10767) [Link]
I'm referring to MySQL's very checkered history. Mostly due to MySQL AB wanting to walk the line between proprietary and Open Source, staying as close to the proprietary side as possible while still gaining FOSS benefits.
Required copyright assignment. Selling proprietary licenses. Keeping some of the features proprietary only. The distros being stuck at MySQL version 3.x for release after release due to MySQL AB's licensing games. The mysql.com vs mysql.org snit.
I've always been a bit surprised that they still have a fan base after all that has happened over the years.
Meanwhile, postgresql.org has just quietly made release after release of topnotch, unmistakably FOSS, RDBMS software, in stark contrast to the soap opera over at mysql.com.
BTW, it's your *real* MySQL over at mysql.com that is in the greatest peril right now. The drama continues...
A look at the MySQL forks Posted Apr 24, 2009 0:52 UTC (Fri) by rahulsundaram (subscriber, #21946) [Link]
Simply put, nothing other than mysql.com is ever going to be called MySQL (trademark and all that) and it doesn't really matter much. Forks are free to take a different path under a different brand and they already have including Drizzle endorsed by Sun. I suspect some of them will just live their own life like many forks such as Emacs and XEmacs have. I see no reason for doom and gloom. In fact, I like the new environment of many experiments.
A look at the MySQL forks Posted Apr 23, 2009 15:13 UTC (Thu) by AdHoc (subscriber, #1115) [Link]
I'd call EnterpriseDB a downstream for PostgreSQL, which AFAIK contributes code back to PostgreSQL.
A look at the MySQL forks Posted Apr 23, 2009 16:06 UTC (Thu) by rahulsundaram (subscriber, #21946) [Link]
That is the case for most, if not all of the MySQL forks as well. Whether you want to call it a fork or a downstream derivative, spoon or something else is your choice.
A look at the MySQL forks Posted Apr 23, 2009 8:54 UTC (Thu) by tzafrir (subscriber, #11501) [Link]
Any of those patches spotted in the wild^W^Win popular Linux distributions?
|
|||||||||||||