5 ms·

MariaDB 10.0 Beta launched

82 points by aritraghosh007 13y ago

cakeface 13y ago
Has anyone done a conversion from mysql to mariadb recently? How was the experience?
- nitrogen 13y ago
  Seamless. I'm not using stored procedures, views, etc., but for some simple InnoDB databases, MariaDB was a drop-in replacement. The command line tools are even still called mysql.
- deweller 13y ago
  I maintain a reasonably complex web app in production that uses stored procedures extensively. I am running it in production with both MariaDB 5.5.x and MySQL 5.5.x. I have not experienced any compatibility issues with MariaDB vs. MySQL.
- SkyAtWork 13y ago
  We're currently doing one. It's been relatively painless, most of the difficulty being simultaneously moving off old myisam tables to innodb -> xtradb
- terrellm 13y ago
  I develop a Rails 3 web app and recently moved from MySQL to MariaDB. Well actually the guys at Rails Machine did the move for me. I don't know what all they did on their end, so can't speak much for the server admin side. We ended up making the switch since I was moving to a high availability setup with multiple DB servers. On the web app side, I am using the mysql2 gem and made zero changes to my code. Also, I frequently import SQL dumps from MariaDB into my local MySQL development with no problems. The only issue I had was related to some nasty SQL I had in a select in a finder (yeah I know bad practice). MySQL was returning a 0 while MariaDB returned NULL. Either way, it was my fault for messy code and when I fixed the select, everything was good.
  - viraptor 13y ago
    There's one silly difference I noticed. Timestamps in mariadb dumps have their size appended. Mysql doesn't like that, so you need to filter them out. Otherwise pretty much a drop-in.
- simonz05 13y ago
  Recently upgraded from MySQL 5.1 -> MariaDB 5.5 with no issues what so ever. We have ~90 tables where the largest table has 40,000,000 entries. I configured the new database servers as slaves of the old ones. This enabled me to verify things in production and do a safe upgrade. Promoting the MariaDB slaves to master was the only required action in terms of switching over. No code changes were required in our application code.
- treffer 13y ago
  We were thinking about it. I fired up our apps testsuite and found a bug: https://mariadb.atlassian.net/browse/MDEV-4711 https://mariadb.atlassian.net/browse/MDEV-4711 The bug was now been analyzed but not fixed for ~3 releases. That said I also ran the testsuite against 5.6 and found some problems, too. You might also be concerned about http://bugs.mysql.com/bug.php?id=69274 http://bugs.mysql.com/bug.php?id=69274 - this means that if you loose an idb file during a crash you're out of luck to use your db ever again. We're thus currently stuck at percona server 5.5 with regular investigation of the alternatives.
darkchasma 13y ago
I've been impressed with Postgres, and still have a sour taste in my mouth over MySql's sale to Oracle. So why would I want to use MariaDB over Postgres? Is there a compelling reason to give it a look?
- nivla 13y ago
  The main stronghold of MariaDB is the drop in replacement for MySQL. If you already have a well established web app and you are planning on get off the clutches of Oracle, MariaDB is your easy choice. You don't have to make substantial changes or worry about breaking any existing functionality. As for performance, can someone who have used both comment on it? Also anyone knows if any exciting changes coming to MYSQL? Can't believe MySQL still doesn't have support for Json.
  - tony_landis 13y ago
    I am pleased to see that the traditional SQL databases are still advancing. Having used various NoSQL databases, I always miss the declarative nature of SQL. I have to agree that MariaDB's main stronghold being MySQL drop in. The other MySQL drop in out there is MemSQL, which is closed and they really keep pricing under wraps. TokuDB is a great engine. I don't think Postgres has a storage engine that matches the benefits TokuDB brings, but other than that I don't see many benefits over Postgres for a new project, but haven't compared the replication features closely. Migrating a big codebase to Postgres from MySQL can be kind of a pain unless everything wrapped everything in an ORM like sqlalchemy. The main pain point for me in a recent migration was how postgres handles mixed case in table/column names. Most of the function differences between the two are fairly easy to resolve. Can anyone with experience with JSON in both Postgres and MariaDB make a comparison?
    - porker 13y ago
      > TokuDB is a great engine. I don't think Postgres has a storage engine that matches the benefits TokuDB brings I have heard about TokuDB but I can't find any good resources to explain why it's so good and what it does differently. Do you know of any? The page on the MariaDB site (linked to from the OP) says very little... Thanks!
kijin 13y ago
DELETE ... RETURNING Cool! The ability to fetch the result of a write operation without having to do a SELECT afterward is one of my favorite "minor perks" of PostgreSQL. It eliminates the need for a lot of extra queries. With MariaDB 10.0, only DELETE statements get the RETURNING clause. But it seems that they have plans to add it to UPDATE statements soon [1], and I hope INSERT gets it as well. [1] https://mariadb.atlassian.net/browse/MDEV-5092 https://mariadb.atlassian.net/browse/MDEV-5092
antihero 13y ago
What is involved in changing from 5.5 to 10.x?

Has anyone done a conversion from mysql to mariadb recently? How was the experience?

nitrogen 13y ago
Seamless. I'm not using stored procedures, views, etc., but for some simple InnoDB databases, MariaDB was a drop-in replacement. The command line tools are even still called mysql.
deweller 13y ago
I maintain a reasonably complex web app in production that uses stored procedures extensively. I am running it in production with both MariaDB 5.5.x and MySQL 5.5.x. I have not experienced any compatibility issues with MariaDB vs. MySQL.
SkyAtWork 13y ago
We're currently doing one. It's been relatively painless, most of the difficulty being simultaneously moving off old myisam tables to innodb -> xtradb
terrellm 13y ago
I develop a Rails 3 web app and recently moved from MySQL to MariaDB. Well actually the guys at Rails Machine did the move for me. I don't know what all they did on their end, so can't speak much for the server admin side. We ended up making the switch since I was moving to a high availability setup with multiple DB servers. On the web app side, I am using the mysql2 gem and made zero changes to my code. Also, I frequently import SQL dumps from MariaDB into my local MySQL development with no problems. The only issue I had was related to some nasty SQL I had in a select in a finder (yeah I know bad practice). MySQL was returning a 0 while MariaDB returned NULL. Either way, it was my fault for messy code and when I fixed the select, everything was good.
- viraptor 13y ago
  There's one silly difference I noticed. Timestamps in mariadb dumps have their size appended. Mysql doesn't like that, so you need to filter them out. Otherwise pretty much a drop-in.
simonz05 13y ago
Recently upgraded from MySQL 5.1 -> MariaDB 5.5 with no issues what so ever. We have ~90 tables where the largest table has 40,000,000 entries. I configured the new database servers as slaves of the old ones. This enabled me to verify things in production and do a safe upgrade. Promoting the MariaDB slaves to master was the only required action in terms of switching over. No code changes were required in our application code.
treffer 13y ago
We were thinking about it. I fired up our apps testsuite and found a bug: https://mariadb.atlassian.net/browse/MDEV-4711 https://mariadb.atlassian.net/browse/MDEV-4711 The bug was now been analyzed but not fixed for ~3 releases. That said I also ran the testsuite against 5.6 and found some problems, too. You might also be concerned about http://bugs.mysql.com/bug.php?id=69274 http://bugs.mysql.com/bug.php?id=69274 - this means that if you loose an idb file during a crash you're out of luck to use your db ever again. We're thus currently stuck at percona server 5.5 with regular investigation of the alternatives.

I've been impressed with Postgres, and still have a sour taste in my mouth over MySql's sale to Oracle. So why would I want to use MariaDB over Postgres? Is there a compelling reason to give it a look?

nivla 13y ago
The main stronghold of MariaDB is the drop in replacement for MySQL. If you already have a well established web app and you are planning on get off the clutches of Oracle, MariaDB is your easy choice. You don't have to make substantial changes or worry about breaking any existing functionality. As for performance, can someone who have used both comment on it? Also anyone knows if any exciting changes coming to MYSQL? Can't believe MySQL still doesn't have support for Json.
- tony_landis 13y ago
  I am pleased to see that the traditional SQL databases are still advancing. Having used various NoSQL databases, I always miss the declarative nature of SQL. I have to agree that MariaDB's main stronghold being MySQL drop in. The other MySQL drop in out there is MemSQL, which is closed and they really keep pricing under wraps. TokuDB is a great engine. I don't think Postgres has a storage engine that matches the benefits TokuDB brings, but other than that I don't see many benefits over Postgres for a new project, but haven't compared the replication features closely. Migrating a big codebase to Postgres from MySQL can be kind of a pain unless everything wrapped everything in an ORM like sqlalchemy. The main pain point for me in a recent migration was how postgres handles mixed case in table/column names. Most of the function differences between the two are fairly easy to resolve. Can anyone with experience with JSON in both Postgres and MariaDB make a comparison?
  - porker 13y ago
    > TokuDB is a great engine. I don't think Postgres has a storage engine that matches the benefits TokuDB brings I have heard about TokuDB but I can't find any good resources to explain why it's so good and what it does differently. Do you know of any? The page on the MariaDB site (linked to from the OP) says very little... Thanks!

kijin 13y ago

DELETE ... RETURNING Cool! The ability to fetch the result of a write operation without having to do a SELECT afterward is one of my favorite "minor perks" of PostgreSQL. It eliminates the need for a lot of extra queries. With MariaDB 10.0, only DELETE statements get the RETURNING clause. But it seems that they have plans to add it to UPDATE statements soon [1], and I hope INSERT gets it as well. [1] https://mariadb.atlassian.net/browse/MDEV-5092 https://mariadb.atlassian.net/browse/MDEV-5092

antihero 13y ago

What is involved in changing from 5.5 to 10.x?