News for hackers. Stuff that matters.

A comment on Babelfish: SQL Server-to-Postgres Translation Layer. Parent comment

Re:Babelfish: SQL Server-to-Postgres Translation Layer by pletnes on Tuesday December 01, 2020 @02:18PM (#25268728)
For SQL server, AWS can save their customers money by cutting license cost (to MS). MySQL is already free so I don’t see how they can benefit from such a project.
[ Parent | on HN ]
Re:Babelfish: SQL Server-to-Postgres Translation Layer by bbatha on Tuesday December 01, 2020 @11:29PM (#25273272)
They can go one better — they can fork the parsers out of both projects and run it against a common query planner/storage engine (aurora).
[ Parent | on HN ]
Re:Babelfish: SQL Server-to-Postgres Translation Layer by jcriddle4 on Wednesday December 02, 2020 @08:52PM (#25284306)
If you have several thousand stored procs and triggers then having to not rewrite all of that is actually likely over a million in savings.
[ Parent | on HN ]
Re:Babelfish: SQL Server-to-Postgres Translation Layer by etaioinshrdlu on Tuesday December 01, 2020 @02:52PM (#25269094)
I agree, but there might be a creative way to do it that increases customer happiness and still is a decent business.
[ Parent | on HN ]
Re:Babelfish: SQL Server-to-Postgres Translation Layer by ksec on Wednesday December 02, 2020 @12:44AM (#25273598)
>don’t see how they can benefit from such a project

I thought there were bad blood between Oracle and Amazon?

[ Parent | on HN ]
Re:Babelfish: SQL Server-to-Postgres Translation Layer by jen20 on Thursday December 03, 2020 @01:32PM (#25292597)
In that case you'd expect to see it for Oracle proper instead of MySQL first, no?
[ Parent | on HN ]
Re:Babelfish: SQL Server-to-Postgres Translation Layer by rj0049 on Thursday December 03, 2020 @10:05PM (#25298444)
The Oracle wire protocol contains a (copyrighted) haiku, so no one can reverse-engineer the Oracle wire protocol without infringing on Oracle's copyright.
[ Parent | on HN ]