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.
MariaDB is a drop in replacement for MySQL which was forked a while ago: http://mariadb.org/
in girum imus nocte et consumimur igni
You mean, like MariaDB, as mentioned in the summary (hint: 3rd word) ?
MySQL is lighter than PostgreSQL.
SQLite is an embeded database; it's really a different sort of tool altogether.
WHY is still anyone using mysql, when there is Postgresql?
I've tried numerous times to drive a car, and every time i found it less easy than the motorcycle which i'm used to for 10 years.
Therefore, from an objective point of view it can be concluded that cars are more difficult to drive than motorcycles.
Thanks for listening, so where's my +5 Insightful like parent has?
CLI paste? paste.pr0.tips!
You are very right. MySQL is like PHP. That's why people shouldn't use both.
Avoid stuff where you can have bugs like this:
http://bugs.mysql.com/bug.php?id=31001
http://pwnhome.wordpress.com/2011/08/22/php-crypt-bug/
http://me.veekun.com/blog/2012/04/09/php-a-fractal-of-bad-design/
And watch the MySQL jokers try to fix this:
http://bugs.mysql.com/bug.php?id=65111
And somehow cause this:
http://bugs.mysql.com/bug.php?id=65745
I'm a crap programmer, but I prefer to use libraries, tools and languages that are less crap than my stuff. That way at least I spend more time dealing with my own incompetence than someone else's.
The database really isn't that important. It only becomes important once a DBA gets their hands on it and starts implementing LOGIC at the database instead of doing the logic in the application and fast, dumb, simple queries at the database.
That is not true at all. In fact wildly wrong. A good database is the tool you use to manage your data. If your system is properly designed, it is part of your application. A good database will manage concurrency, data integrity, and more. The idea that you move this out into the application geometrically increases complexity, or more likely, is ignored at your peril.
Just a simple query:
select * from songs where name like 'love%';
Assuming you have a non-trivial amount of songs, i.e. a song web site, this query can show a poorly implemented index. Once you start getting into sub-selects and joins, a good database can do quite well, a bad database, i.e. MySQL will fall down.
People who view the database as nothing but dumb storage usually end up implementing similar features in their code. They won't be as efficient, won't be standard, will cause the data to be processed more than it needs to be, and can't be tested as well as the database's system.
A good architect will know where and when it makes sense to do something in a database verses the application. Ignoring the capabilities of a database for some idealogical purity is ridiculous.