It will be a success when it fully supports, Object Types, Packages, Autonomous transactions, PL/SQL, and BULK Collect Operations among other features.
IvorySQL: Open-source Oracle-compatible PostgreSQL
11–20 of 73 posts
Re: IvorySQL: Open-source Oracle-compatible PostgreSQL
#12I don't get what this is. Is this a postgres fork? An extension? The documentation says it's Version 2 but the docs are rather lacking. Having something providing an "Oracle API" on Postgres would be awesome but not sure if this works like that?
Can someone elaborate on what specifically something like this would be used for?
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?
Re: IvorySQL: Open-source Oracle-compatible PostgreSQL
#13Wiped out by Oracle's legal team (patents, whatever) in 4...3...2...
Re: IvorySQL: Open-source Oracle-compatible PostgreSQL
#14I don't get what this is. Is this a postgres fork? An extension? The documentation says it's Version 2 but the docs are rather lacking. Having something providing an "Oracle API" on Postgres would be awesome but not sure if this works like that?
Can someone elaborate on what specifically something like this would be used for? 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 replace…
Full migration can take months if not years. Meanwhile, a drop-in replacement will allow you to stop paying Oracle immediately.
I wouldn't be too optimistic about ORM usage in the kinds of organizations that chose Oracle in the first place.
Re: IvorySQL: Open-source Oracle-compatible PostgreSQL
#15Great choice of name and logo.
Re: IvorySQL: Open-source Oracle-compatible PostgreSQL
#16I don't get what this is. Is this a postgres fork? An extension? The documentation says it's Version 2 but the docs are rather lacking. Having something providing an "Oracle API" on Postgres would be awesome but not sure if this works like that?
Can someone elaborate on what specifically something like this would be used for? 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 replace…
Oracle is expensive. Salesforce has been developing something similar internally for years to replace Oracle.
Re: IvorySQL: Open-source Oracle-compatible PostgreSQL
#17I don't get what this is. Is this a postgres fork? An extension? The documentation says it's Version 2 but the docs are rather lacking. Having something providing an "Oracle API" on Postgres would be awesome but not sure if this works like that?
Can someone elaborate on what specifically something like this would be used for? 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 replace…
If you're using an ORM then you're by default using the database fairly generically. I'd ask why you are paying for any commercial DB in that case.
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.
Re: IvorySQL: Open-source Oracle-compatible PostgreSQL
#18Wiped out by Oracle's legal team (patents, whatever) in 4...3...2...
They haven't hit EnterpriseDB who have been doing the same thing, except not open source, since forever.
Re: IvorySQL: Open-source Oracle-compatible PostgreSQL
#19I don't get what this is. Is this a postgres fork? An extension? The documentation says it's Version 2 but the docs are rather lacking. Having something providing an "Oracle API" on Postgres would be awesome but not sure if this works like that?
Can someone elaborate on what specifically something like this would be used for? 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 replace…
Because migrating off Oracle to an Oracle-compatible DB is less work than migrating to straight Postgres. This is not rocket science.
Re: IvorySQL: Open-source Oracle-compatible PostgreSQL
#20Earlier quoted context omitted.
Can someone elaborate on what specifically something like this would be used for? 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 replace…
If you're using an ORM then you're by default using the database fairly generically. I'd ask why you are paying for any commercial DB in that case. 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 w…
> It's not clear to me that it really can do that, though.
It would seem exceedingly foolhardy to put all your eggs into, what is essentially a compatibility shim layer/plugin, that may or may not actually be compatible with Oracle or all of Oracle.
The company behind it also is an unknown (to me at least) - HiGo[1].
So, IvorySQL is FOSS and free (as in beer) - but what happens if some feature doesn't actually work like advertised? Or something isn't implemented yet? Now you're paying HiGo for support instead of Oracle - although I'd trust Oracle's product a lot more personally.
> I'd ask why you are paying for any commercial DB in that case.
People pay for commercial DB's for a lot of reasons - including having someone to call at 3am when things go bad. Look at how prevalent SQL Server is - most of the deployments I've seen are because the company simply decided they will use SQL Server for everything (ie, not a technical reason).