<story><title>Babelfish: SQL Server-to-Postgres Translation Layer</title><url>https://aws.amazon.com/blogs/opensource/want-more-postgresql-you-just-might-like-babelfish/</url></story><parent_chain><item><author>etaioinshrdlu</author><text>Don&amp;#x27;t hate me for it, but I&amp;#x27;d like this for MySQL to postgres too. At least as a stepping stone.&lt;p&gt;Use case: some of my SQL syntax depends on MySQL but I realize I made a poor life choice and would rather have transactional DDL and a myriad of better features on postgres.</text></item></parent_chain><comment><author>lukaseder</author><text>Use &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.jooq.org&amp;#x2F;translate&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.jooq.org&amp;#x2F;translate&amp;#x2F;&lt;/a&gt;</text></comment>
<story><title>Babelfish: SQL Server-to-Postgres Translation Layer</title><url>https://aws.amazon.com/blogs/opensource/want-more-postgresql-you-just-might-like-babelfish/</url></story><parent_chain><item><author>etaioinshrdlu</author><text>Don&amp;#x27;t hate me for it, but I&amp;#x27;d like this for MySQL to postgres too. At least as a stepping stone.&lt;p&gt;Use case: some of my SQL syntax depends on MySQL but I realize I made a poor life choice and would rather have transactional DDL and a myriad of better features on postgres.</text></item></parent_chain><comment><author>linsomniac</author><text>You might be able to get away with staying with MySQL or a variant.  Years ago I did an &amp;quot;interview problem&amp;quot; to generate a report of some accounting data of a sample data set in MySQL.  The details are foggy now, but I ended up doing it all using advanced SQL features that I thought only existed in PostgreSQL (you know, or Oracle), but whatever engine I ended up using had it as well.  It was probably the latest Percona or Maria?</text></comment>