Slashdot Mirror
MariaDB 10 Released, Now With NoSQL Support
noahfecks (2379422) writes "Version 10 of the most famous fork of MySQL MariaDB has been released. Its developers said that is many times faster than MySQL, also claiming that its replications slaves are crash free. More details of this release can be found on the blog."
I've tried out MariaDB specifically, the Galera Cluster many times and found it to be very lacking. The default Debian repos just seem broken and have been for a long time according to the bug reports i've read. Apart from the broken packages the fact that the documentation is very lacking and dotted all over the place has put me off. After MariaDB I moved on to Percona's implementation which comes with working packages and good documentation.
www.hardwar.org - A remake of the old classic Hardwar
The summary says the replication slaves are now crash free, but TFA says they are crash-safe. My database knowledge doesn't go very deep, but I think the latter means they won't lose data on crashes, not that they never crash.
no idea, but I know Postgresql has had JSON columns for a while now, so you get the benefit of 'typeless' data storage (ie a blob of JSON data) and all the benefit of relational data if you want it (as its just another column).
MariaDB did it differently, merging Cassandra as a storage back-end, and "dynamic columns' so you can have different columns of data per row in a table. (and you can get all the dynamic column data out as a JSON blob).
NoSQL means the same thing it always means, "ACID is hard, so we don't do it."
By that definition, MySQL is the original NoSQL database.
GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
The first item from your link:
He tries to insert 99999999999999 into a 32 bit int field, what he gets is 2147483647 stored as the value.
What do you suppose would happen in C/C++ if you have a 32 bit int, and you add 99999999999999 to it? Are you going to curse C/C++ for allowing the int to overflow?
Allow me to introduce you to strict mode: http://dev.mysql.com/doc/refma...
Which has been available for almost a decade.
You're like a dog with a bone. Last time I worked with MySQL was 5.0.1, and it was letting people insert ASCII strings into integer fields, and every time people expressed concerns, all you saw was rhetoric about how that should have been dealt with at the application layer. Which is fine if you're setting up a web forum, but not when you're organizing an enterprise that spans the world and has numerous applications accessing it, where one junior programmers mistake can hose your whole fucking enterprise. No client has mandated that I MUST use it since, therefore, I haven't used it since, and asked a serious question.
The history of MySQL was very well summed up in an earlier post: "ACID is hard, therefore we don't do it."
Not just me... most professionals know this and accept it and know that not every tool fits every scenario. Don't know what YOUR fucking problem is.
-1 Uncomfortable Truth
I'd always thought MySQL was NoSQL to begin with. "Datatypes? Integrity? What geezer wants those! LOL! We're webscale!"
(I love NoSQL DBs like Cassandra for the right applications. I haven't ever found an application for which I'd love MySQL.)
Dewey, what part of this looks like authorities should be involved?