Slashdot Mirror
Is MySQL Slowly Turning Closed Source?
mpol writes "Sergei from MariaDB speculated on some changes within MySQL 5.5.27. It seems new testcases aren't included with MySQL any more, which leaves developers depending on it in the cold. 'Does this mean that test cases are no longer open source? Oracle did not reply to my question. But indeed, there is evidence that this guess is true. For example, this commit mail shows that new test cases, indeed, go in this "internal" directory, which is not included in the MySQL source distribution.' On a similar note, updates for the version history on Launchpad are not being updated anymore. What is Oracle's plan here? And is alienating the developer community just not seen as a problem at Oracle?"
And is alienating the developer community just not seen as a problem at Oracle?
Pretty much exactly this.
"Is MySQL Slowly Turning TheirSQL?"
Postgresql is also a Free Software multi-platform database. It was designed properly (unlike MySQL, Postgresqlwas designed with transactions in mind), has excellent internationalization support (proper 3 and 4 byte UTF, unlike MS SQL-Server with its UCS-2 or blob unicode [unless the very latest version has fixed this]).
Personally I prefer Postgresql to MySQL. While Postgresql looks more 'plain vanilla' I actually find it more straightforward to get easy things done (that is, pgadminIII doesn't look so flashy but I found it is much easier to get connected and get going than mysqlworkbench). YMMV of course, but if you are concerned about corporate control and the future of MySQL taking a look at Postgresql won't harm you - it is a nice(r) place to land if you have to.
Look, by no means FORK! am I a SQL expert, but I still feel FORK! compelled to express my FORK! opinon here. Face it folks, Oracle FORK! is evil. That said, if there is some way FORK! to create a parallel version, a version FORK! not intended to pay for a yacht, I would FORK! be all for it.
Support microSD: in a post 9/11 world, it is unwise to carry your data on media that you cannot comfortably swallow.
Oracle has been doing nothing more than gobbling competitors the whole time. Just because the haven't done it overnight doesn't mean that's not what they're doing.
Two of my imaginary friends reproduced once
MariaDB is a drop in replacement for MySQL which was forked a while ago: http://mariadb.org/
in girum imus nocte et consumimur igni
Larry Ellison believes in one thing: making money.
If publishing test cases doesn't make money for Oracle and they're not required to do it by law (license, etc) then they won't do it.
Stop pretending Oracle cares about anything other than money and you'll have a much more accurate and healthy view of the beast.
oracle is actually an acronym: One Rich Asshole Ceo, Larry Ellison
I put on my robe and wizard hat..
MySQL is lighter than PostgreSQL.
SQLite is an embeded database; it's really a different sort of tool altogether.
if they want to use open source database. Try Firebird SQL if you want to go light (lighter than mysql in most cases I've seen), or go with the big boys with PostgreSQL.
Shit, I didn't know that! I saw MariaDB and I didn't think to google to find out who or what that is supposed to be.
I guess I'm spoiled by proper editing and writing where it should have been phrased as such:
"Sergei from MariaDB, a MySQL Fork, speculated on some changes within MySQL 5.5.27."
But never mind, we should all google and research everything posted here because, not only do most folks talk out of their asses, but by missing some detail like that gives some pedant a chance to post something to make himself feel superior for knowing some esoteric and minor piece of information.
SQLite is an embeded database; it's really a different sort of tool altogether.
But you don't have to use it embedded. The command line tool is basic but functional, and if you want, say, a web interface to query a SQLite back end, you can do that too. For most of the MySQL use cases, there's really not much difference.
I worked as a MySQL DBA for years, and I was quite vocal in its defense. Eventually I realized that most of the criticisms of it were entirely reasonable (even if the tone in which they were expressed often wasn't) and that OP is right: use SQLite for stuff that's, well, light, and Postgres for anything that's heavier-duty. The only arguments for MySQL these days are its ubiquity and extensive documentation, and the way Oracle's behaving I don't expect either of those will apply much longer.
The correlation between ignorance of statistics and using "correlation is not causation" as an argument is close to 1.
What if Oracle is planning to slowly slowly kill off/degrade MySQL? By with-holding the test cases / not putting in effort into new features/development. If opensource contributors cant test properly - they would create a buggy, unstable/inferior product in the future. According to what I know - Oracle is in the database business, MySQL is "competing" database of sorts... Why would oracle want to keep it around? Its not in their interest, right?
WHY is still anyone using mysql, when there is Postgresql?
Forking worked for Libreoffice, I dont see why it couldn't work for MySQL...
in the title of a story.
would prevent a lot of bad written summaries.
I believe it is One Rich Asshole Called Larry Ellison
This would double overnight if MySQL were declared pariah non grata, which is precisely the negotiation taking place in this kind of discussion thread.
Speaking of PNG, you do recall the Unisys GIF debacle? When MySQL dies, may its tombstone read G.I.F.