- Security issues (SSL problems)
- Broken Unicode support
- Placeholders, support for new client versions,
- Real vulnerabilities with names, logos, and pages!
- DBD::MariaDB refuses to connect using vulnerable client
library when SSL is required.
In mysql, you can specify
- the server encoding
- encoding of the default database
- encoding of the statement sent by the client
- encoding to translate an incoming statement to
- encoding of the result sent to the client
- encoding for a particular table
- encoding for a particular column…
Unicode support (2)
utf8 in mysql is 3-byte, to use all 4 bytes,
- Previously, Latin-1 was the default, now UTF-8 if
possible, otherwise the 3-byte UTF-8
- UTF-8 support for placeholders was broken:
utf8 needs to be followed by a call
in C which was missing
Unicode support (3)
- By default, DBD::MariaDB uses Perl Unicode characters.
- Originally, just a patch to DBD::mysql, but old code
depending on old buggy behaviour might not work with the
Backlash of legacy code maintainers ⇒ we forked the driver.
Testing in Travis-ci.org
137 different combinations of Perl, client, and server versions
BTW, we are hiring!