IvorySQL: Open-source Oracle-compatible PostgreSQL
github.com
github.com
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.
http://www.rcfp.org/sites/default/files/docs/20120105_202426... is when Apple tried to get the haiku protected as a trade secret
Bonus fun fact: Once the “don’t steal Mac OS” kext is loaded, a longer poem is loaded into memory (at least, it was around Tiger):
Your karma check for today:
There once was was a user that whined
his existing OS was so blind,
he’d do better to pirate an OS that ran great
but found his hardware declined.
Please don’t steal Mac OS! Really, that’s way uncool.
(C) Apple Computer, Inc.
(https://www.zdnet.com/article/apple-warns-off-os-pirates-wit...)
Is it illegal to recite a copywrited work? Is it illegal to recite a translation of a copywrited work?
Can you copyright a number? For instance, a long binary number? If a piece of code contains a long binary number that it transmits to another device as a raw number, does it matter if the other device can arbitrarily interpret that number as a copyrighted work using SJIS or ASCII or some tortured encoding created just to turn a specific number into a specific copyrighted work? If the number was stored in UTF8 so that each 1 was encoded as 00000001 then decoded to a 1 for transmission, can you really claim any copywrite violation?
And why does my brain waste time thinking up such questions?
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.
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.
I don't know where to find it on their website, but the docs RPM that they provide bundles the PDF.
However, few people actually use Pro*C nowadays. I spent almost 10 years working for Oracle, and I never once came across anybody using it. I think almost all use of it is in legacy applications which date back to the 1980s, first half of the 1990s at the latest. Obviously still enough use for Oracle to keep on supporting it, even with some occasional minor enhancements, but rather fringe all the same.
I don't think many people use ECPG either. I'm sure some people must, but I myself have never seen it. Probably most use is in porting existing applications from Oracle Pro*C, or its equivalents such as Informix E/SQL. Actually, it is interesting to observe that the section on ECPG's Informix compatibility mode is a lot longer than the Oracle equivalent. I don't know if that's because less compatibility is required (maybe Pro*C is closer to ECPG already), or if that's because Informix compatibility has received more investment.
https://www.enterprisedb.com/products/edb-enterprise
The difference here is that the EnterpriseDB product is not open source.
https://www.enterprisedb.com/resources/ibmr-puts-oracle-swor...
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.
Oddly, I'd take their compatibility claims more seriously if they were more clearly up-front about the limits.
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.
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).
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 bad.
Oh, the old support excuse for proprietary software. The Oracle support is excellent, but good hope getting anybody to help you at 3am. Good luck getting anybody to actually help you in less than 24 hours anyway. None of the big proprietary software distributors offer anything like this. Oracle is way ahead of the competition on that they will even actually help... kind like you get when you hire a local company to support Postgres for you.
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 at 3am, and even have a service technician onsite in the morning if needed. Personal experience with this one - they'll fly someone in from out of state to replace a hard drive if it means meeting their service levels.
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.
It's a big win even if it just substantially reduces the transition cost, though being completely drop-in would be even better.
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.
You are wrong; from the Babelfish page: “With Babelfish, Aurora PostgreSQL now understands T-SQL, Microsoft SQL Server's proprietary SQL dialect, and supports the same communications protocol, so your apps that were originally written for SQL Server can now work with Aurora with fewer code changes.”
> 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.
Postgresql, on the other hand, is dead simple to manage.
It's my dream to move all my Oracle databases to Postgresql.