Hacker News new | ask | show | jobs
by devit 2244 days ago
How come nobody has implemented an Oracle compatibility mode for PostgreSQL?

Or in general, why don't databases support each others SQL dialect? It can't be that much work, at least if one is content with only supporting the majority of applications, and seems pretty essential for popularizing a specific database.

Looking at the article, supporting Oracle syntax seems trivial in all cases except for adding full MERGE support.

3 comments

You mean like...

https://www.enterprisedb.com/enterprise-postgres/database-co...

It's been around for years. Earlier on PostgreSQL did make some efforts of being recognizable to Oracle users... look at Oracle PL/SQL and PostgreSQL PL/pgSQL... very similar and I recall that similarity being intentional.

Also, there is the SQL standard. Rather than supporting all vendors' syntax and features, which can change on the whim of some competitor that probably doesn't have your best interests at heart, it's better to adhere to the standard if you want the broadest applicability. PostgreSQL does exactly that with few deviations from the standard, relative to the industry as a whole. At the end of the day it's really about goals and not every RDBMS has the same goals; with PostgreSQL standards compliance is a goal.

Two reasons.

> It can't be that much work

You're right, IF you so overly simplify the translation that it also doesn't work with the majority of Oracle applications.

Second: Have you heard of the Android/Java/API lawsuit?

> It can't be that much work,

Seriously?

Syntax is always the trivial part, everywhere you look. Semantics is what bites you.