I presume this still requires the postgres drivers to connect but then just accepts Oracle syntax once connected? That seems like a very specialized replacement case -- where I guess the app has a lot of complex reporting logic or a monster amount of stored procs that can't be changed, but the consuming app(s) can change drivers and exception handling for the PG ones
IvorySQL: Open-source Oracle-compatible PostgreSQL
71–73 of 73 posts
Re: IvorySQL: Open-source Oracle-compatible PostgreSQL
#72Re: IvorySQL: Open-source Oracle-compatible PostgreSQL
#73Earlier quoted context omitted.
If you want to use this, you will port your code, run your tests, fix an issue here or there as needed, and develop for Postgres for now on. None of those steps is particularly risky. If any of the steps that may fail brings an insurmountable obstacle, you ditch the project and go back to where you started. > People pay for commercial DB's for a lot of reasons - including having someone to call at 3am when things go…
The scale of your operation and license subscriptions matters for the level of support you receive, naturally. Big Microsoft shops, like state governments routinely have Microsoft staff fly out and work closely to bring new services online, etc. You cannot expect that level of service if you're just paying for a single database instance, of course. IBM's support is also legendary - you will get a person on the phone…
> you will get a person on the phone at 3am
And that person will do nothing else but waste your time.
What is the natural result of any interaction with Microsoft support too. Not limited to 3am calls.
Anyway, I wonder how RedHat has adapted to the IBM culture. I haven't dealt with software support for a while now, what I'm very grateful for.