Live data from Hacker News

IvorySQL: Open-source Oracle-compatible PostgreSQL

github.com

51–60 of 73 posts

Re: IvorySQL: Open-source Oracle-compatible PostgreSQL

#51

What’s the point of doing some just for the sake of destroying other people’s business?

Oracle requires a lot of maintenance and is terribly buggy. And the documentation is not always complete.

Postgresql, on the other hand, is dead simple to manage.

It's my dream to move all my Oracle databases to Postgresql.

Re: IvorySQL: Open-source Oracle-compatible PostgreSQL

#52

It will be a success when it fully supports, Object Types, Packages, Autonomous transactions, PL/SQL, and BULK Collect Operations among other features.

Oracle Apex will have to be considered too.

It's undeniably a good platform for developing applications and firms get hooked on it.

Re: IvorySQL: Open-source Oracle-compatible PostgreSQL

#53
post #47
post #35

Earlier quoted context omitted.

The software license will still stop you from doing that. No business that would need Oracle will run Oracle software knowingly violating the license.

It’s also likely in violation of arcane copyright law. The oracle wire protocol includes a handshake procedure that sends a poem in one of the initial messages. It’s untested legal theory whether copying that poem in a new work (e.g. a new driver or compatability layer) would violate Oracle’s copyright on the poem. https://dacut.blogspot.com/2008/03/oracle-poetry.html

Very interesting. But I think there are pretty clear rules that permit compatible implementation of wire protocols.

Re: IvorySQL: Open-source Oracle-compatible PostgreSQL

#54
post #18
post #13

Wiped 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.

To my knowledge IBM's DB2 too has an "Oracle compatibility" switch that makes it also support PL/SQL.

Re: IvorySQL: Open-source Oracle-compatible PostgreSQL

#55
post #49

Earlier quoted context omitted.

Postgres has it https://www.postgresql.org/docs/current/rules-materializedvi...

Not as nice as oracle, oracle provides auto refreshed materialized views that will be updated with every commit.

https://www.postgresql.org/about/news/pg_ivm-10-released-244...

Re: IvorySQL: Open-source Oracle-compatible PostgreSQL

#56
post #36

Earlier quoted context omitted.

The postgres 15 manual has a chapter on Oracle compatibility. I don't know where to find it on their website, but the docs RPM that they provide bundles the PDF.

You are probably thinking of ECPG's "Oracle compatibility mode", which makes it behave more like Oracle Pro*C - https://www.postgresql.org/docs/15/ecpg-oracle-compat.html 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…

I've used pro* C for a couple of things (in banking and utilties, 1990s) where people wanted interactive batch functionality for something more complex than you'd generally put in a shell script. I think most of the pro* C usage came from pre Oracle 7 when PL/SQL didn't exist.

Re: IvorySQL: Open-source Oracle-compatible PostgreSQL

#57

It will be a success when it fully supports, Object Types, Packages, Autonomous transactions, PL/SQL, and BULK Collect Operations among other features.

That was my question. Is it compatible with PL/SQL? And how is the performance?

Somebody makes a Postgres variant that supports not only PL/SQL, but supplies a number of the standard DBMS_xyz packages. EnterpriseDB?

Re: IvorySQL: Open-source Oracle-compatible PostgreSQL

#58
post #47
post #35

Earlier quoted context omitted.

The software license will still stop you from doing that. No business that would need Oracle will run Oracle software knowingly violating the license.

It’s also likely in violation of arcane copyright law. The oracle wire protocol includes a handshake procedure that sends a poem in one of the initial messages. It’s untested legal theory whether copying that poem in a new work (e.g. a new driver or compatability layer) would violate Oracle’s copyright on the poem. https://dacut.blogspot.com/2008/03/oracle-poetry.html

Actually I’m pretty sure a lawsuit with Nintendo’s game boy drm (where you needed to have the logo in memory to boot) went to court and it was ruled that if working with the system required copying the copyrighted text then it’s fair use (US, long time ago and in a different but similar concept)

Re: IvorySQL: Open-source Oracle-compatible PostgreSQL

#59
post #47
post #35

Earlier quoted context omitted.

The software license will still stop you from doing that. No business that would need Oracle will run Oracle software knowingly violating the license.

It’s also likely in violation of arcane copyright law. The oracle wire protocol includes a handshake procedure that sends a poem in one of the initial messages. It’s untested legal theory whether copying that poem in a new work (e.g. a new driver or compatability layer) would violate Oracle’s copyright on the poem. https://dacut.blogspot.com/2008/03/oracle-poetry.html

Weird, Apple does a similar thing with macOS startup on Intel (and more recently, Rosetta on Linux). If the magic haiku isn’t given the OS won’t start.

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...)

Re: IvorySQL: Open-source Oracle-compatible PostgreSQL

#60
post #49

Earlier quoted context omitted.

Postgres has it https://www.postgresql.org/docs/current/rules-materializedvi...

Not as nice as oracle, oracle provides auto refreshed materialized views that will be updated with every commit.

Isn't that better accomplished as an ordinary view + an index (arguably, an "auto-refreshed materialized" store is an index)? AIUI, Postgres supports indexes on arbitrary expressions.
Post reply on HN