Can you imagine just swapping in Postgres under a Peoplesoft deployment? As long as you don't make me actually attempt it, it makes me chuckle.
It's undeniably a good platform for developing applications and firms get hooked on it.
"SQL/PSM is derived, seemingly directly, from Oracle's PL/SQL. Oracle developed PL/SQL and released it in 1991, basing the language on the US Department of Defense's Ada programming language."
https://en.m.wikipedia.org/wiki/SQL/PSM
They can always wipe out the Ada programming language while they're at it.
Sounds and looks like a fork to me.
EnterpriseDB used to offer some Oracle compatibility built on Pg, as a fork IIRC. Don't see it on their site any more though.
EDIT: Much thanks to replies with links to EDB.
Oddly, I'd take their compatibility claims more seriously if they were more clearly up-front about the limits.
I understand why upstream Postgres might not want to put Oracle compatibility in the core, since it would be adding a lot of crud which only a minority of people would benefit from. However, making sure the Postgres core has the extension points necessary to support extensions providing compatibility with Oracle (or DB2, MSSQL, MySQL, etc), is something they might be more willing to entertain.
https://www.enterprisedb.com/products/edb-enterprise
The difference here is that the EnterpriseDB product is not open source.
Think of a gnu/linux distro, that gives you some pre-packaged software built with an intended goal (more or less general) and according to a certain set of opinions.
I would imagine if you're going through the pain of migrating off Oracle, picking something like IvorySQL is just a half-measure. Why not just make the switch to PostgreSQL (or other) and be done with worrying about compatibility? How long will this project last, and how great will the compatibility actually be - is it a drop-in replacement?
Most folks use ORM's these days too - making switching databases simple (although not always trivial).
So why does this need to exist?
I wouldn't be too optimistic about ORM usage in the kinds of organizations that chose Oracle in the first place.
Organizations who committed to and paid for Oracle are probably using a lot of the features that are unique to Oracle. Or they have a lot of legacy that is.
If IvorySQL can take all their custom plsql packages and ETL batch jobs and run them without changes that's a big win. It's not clear to me that it really can do that, though.
If you could "just switch" then you probably shouldn't be using RDBMS at all.
it has to be in oracle or pg compatibility mode, so effectively its just an oracle api replacement, but should more or less behave like oracle
so the only primary benefit is you stop paying oracle because you just want to leave oracle?
It doesn't exactly let you move away from oracle APIs though.
It is a big win financially. So good on them, I hope it gets all the traction!
https://en.m.wikipedia.org/wiki/Tabular_Data_Stream
I use freetds in many places.
I don't think that the programming language inside Sybase/Microsoft SQL Server, known as Transact-SQL, has been implemented in postgres, but I could be wrong.
https://en.m.wikipedia.org/wiki/Transact-SQL
Microsoft does not implement SQL/PSM in SQL Server. They need to do so. Immediately.
Postgresql, on the other hand, is dead simple to manage.
It's my dream to move all my Oracle databases to Postgresql.
> What’s the point of doing some just for the sake of destroying other people’s business?
Apart from any potential ideological reasons related to open source, they are likely planning to support their own business by providing a compelling product.
