As someone who has been fighting with a SQL Server to Postgresql conversion this sounds AMAZING. Too bad it won't be available before my conversion is complete (and if it is, that's an even sadder proposition)
Babelfish: SQL Server-to-Postgres Translation Layer
11–20 of 118 posts
Re: Babelfish: SQL Server-to-Postgres Translation Layer
#12Why not do this for Oracle? I've not found SQL Server to be too bad from the crazy Oracle stuff (light experience only - maybe bigger players have it worse?).
Re: Babelfish: SQL Server-to-Postgres Translation Layer
#13Why not do this for Oracle? I've not found SQL Server to be too bad from the crazy Oracle stuff (light experience only - maybe bigger players have it worse?).
As a DBA, T-SQL is much more standard then PL/SQL. Its probably step 1 of the plan, with step 2 being Oracle.
Re: Babelfish: SQL Server-to-Postgres Translation Layer
#14Why not do this for Oracle? I've not found SQL Server to be too bad from the crazy Oracle stuff (light experience only - maybe bigger players have it worse?).
About 10 years back my company hired consultants, spent close to 6 months translating SQL queries/stored procs to be Oracle. The goal was to support both MSSQL Server & Oracle for the on-premise product. It was quite costly undertaking. Then few years later they just abandoned Oracle because of maintenance costs.
I wonder if anyone starting out today chooses Oracle as their relational database.
Re: Babelfish: SQL Server-to-Postgres Translation Layer
#15Any idea what language it’s written in?
Re: Babelfish: SQL Server-to-Postgres Translation Layer
#16Don't hate me for it, but I'd like this for MySQL to postgres too. At least as a stepping stone.
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.
Re: Babelfish: SQL Server-to-Postgres Translation Layer
#17Any idea what language it’s written in?
"Babelfish is written in C, which is the same programming language used to develop PostgreSQL. Some parts of Babelfish are developed using procedural language in PL/pgSQL. Many test cases are written in PL/pgSQL and T-SQL."
Re: Babelfish: SQL Server-to-Postgres Translation Layer
#18Why not do this for Oracle? I've not found SQL Server to be too bad from the crazy Oracle stuff (light experience only - maybe bigger players have it worse?).
Oracle has peculiarities that you won't see in most other databases, which may make this a bit harder -- including such things as an oddball set of date/time types ("date" includes time to seconds), and treating zero length strings as SQL nulls --
'' is null
Re: Babelfish: SQL Server-to-Postgres Translation Layer
#19Earlier quoted context omitted.
Interesting. Now where's the Oracle-to-Postgres Translation project? ;-)
Their legal team might still be preparing for this one given Oracle's reputation.
SCOTUS hasn't yet ruled on Google LLC v. Oracle America Inc. One imagines that if Oracle prevails in some demonstrative manner they may very well believe their flavor of SQL is a software interface protected by copywrite.
So will all the other 'software interface' owners of the world.
Re: Babelfish: SQL Server-to-Postgres Translation Layer
#20Any idea what language it’s written in?
"Babelfish is written in C, which is the same programming language used to develop PostgreSQL. Some parts of Babelfish are developed using procedural language in PL/pgSQL. Many test cases are written in PL/pgSQL and T-SQL."
Argh, I scanned the article multiple times and missed that section. Thank you