If it helps, I've been using MariaDB recently.
It's just about a drop-in replacement for MySQL and I haven't had any such issues with the latest version.
| [reply] |
just about a drop-in replacement for MySQL
Since they forked, MySQL and MariaDB have diverged quite a bit...of course, they both support the core SQL language specification but that still leaves lots of room for differences.
We use MySQL Workbench for creating visual ERDs and building the DDL for the databases. There isn't an alternative for MariaDB that I'm aware of. An immediate problem with using this for MariaDB is that the MySQL tool adds the VISIBLE keyword to indexes. MySQL uses VISIBLE and INVISIBLE whereas MariaDB has visible indexes (with no keyword) and IGNORED indexes.
Plus, our main production database mostly uses the Aria table engine, which isn't available in MySQL. It also uses temporal tables which have a vastly different implementation between MySQL and MariaDB.
In short, MariaDB is far from drop-in replacement for MySQL for anything beyond the simplest use case.
| [reply]
[d/l]
[select] |
And then there is the one massive distinction: one of these is owned, controlled and sold by Oracle and the other isn't and almost certainly never will be.
We've been using MariaDB (and DBD::MariaDB) for almost 10 years now. It has been a bit ahead of MySQL in a few areas of interest to us but the really important part is that it is properly open source and therefore isn't going away (or being restricted or whatever) at the whim of a notorious corporation.
| [reply] |
If you decide to give it another try at some point, add mysql_ssl=1 to your data source like so:
DBI->connect('dbi:mysql:mysql_ssl=1;database=jobs_db','Poster','Poster
+passwd')
| [reply]
[d/l] |
