4 ms·

Zero code changes? No matter how complex and MySQL specific the logic is?

• paulryanrogers 3y ago
  Well there are other Pg extensions that port MySQL specific functions and PL/PSM. One may even be able to leverage rules to rewrite certain syntax differences like intervals. (I saw such a project for an effort to partially support TSQL.)
• nick238 3y ago
  Probably something like an "80% of applications can be supported with 20% of the MySQL-specialized flavor", which is probably closer to 90/10, and those 90% of applications account for 99.9% of MySQL installations.
• aerzen 3y ago
  This is probably referring to "zero changes to your driver code" and not "zero changes to the SQL you send over this driver". Translating between SQL dialects is notoriously hard and attempts to translate [1] are working in 95% of cases. But the last 5% would require 5x amount of work. That's because "SQL dialect" also includes weird edge cases of type inference of things like COALESCE(5, FALSE) and emulation of system catalogs (pg_catalog, information_schema). [1] https://github.com/tobymao/sqlglot https://github.com/tobymao/sqlglot
• gregw2 3y ago
  I agree with the skepticism behind your question. I’ve used both at different firms heavily over the years. I’ll believe it when I see it. What about MySQL’s local @ variables… is that supported in Postgres? I guess they do say they will support MySQL’s procedural language… is there a difference between that and MySQL stored procedure compatibility?