3 ms·

Probably related to the mariadb company debacle. Without mentioning how Mariadb made changes in the last months and years to make it incompatible with mysql

• SteveNuts 3y ago
  Wasn't that the entire point of Maria? Why did they do that this is the first I've heard of that
  • cinntaile 3y ago
    API parity with your competitor is hardly a viable, long-term strategy.
    • SteveNuts 3y ago
      Why not? It's worked for Postgres for a long time. The key is to make "API compatibility" table stakes and add value on top of it.
      • cinntaile 3y ago
        That's definitely a possible strategy, I was (naively) considering a situation where they didn't add a lot of value on top of it.
  • evanelias 3y ago
    No, MariaDB is a fork and has meaningful functionality differences from MySQL. They've been diverging for over a decade and aren't drop-in replacements for each other. Meanwhile Percona Server is a drop-in replacement for MySQL, essentially it's a large patch-set on top of MySQL rather than a fork. Percona Server releases line up with MySQL releases and versioning. Whenever Percona Server features break binary compatibility, it's explicitly noted in their manual, and not enabled by default.
• 0cf8612b2e1e 3y ago
  Was the MySQL change pro or anti consumer? From the sidelines it has been surprising that Oracle has not been doing more to strangle the product.
• mst 3y ago
  Is it actively incompatible or are MySQL and MariaDB both just continuing to develop by implementing slightly different subsets of PostgreSQL (reading change lists for the two of them feels a lot like that from my pg-biased POV).