On 01/11/2017 04:12 PM, Craig Ringer wrote:

What aspects / features of packages were the key issues?

Unfortunately we didn't get too far into it because the webinar was about Postgres specifically. That said, I have been doing some followup. Here is some of it:

because packages[1]

o break the dependency chain (no cascading invalidations when you install a new package body -- if you have procedures that call procedures -- compiling one will invalidate your database)

o support encapsulation -- I will be allowed to write MODULAR, easy to understand code -- rather then MONOLITHIC, non-understandable procedures

o increase my namespace measurably. package names have to be unique in a schema, but I can have many procedures across packages with the same name without colliding

o support overloading

o support session variables when you need them

o promote overall good coding techniques, stuff that lets you write code that is modular, understandable, logically grouped together....

Note: I am not arguing the technical merits here. My goal is 100%, how do we get Oracle folks a true Open Source Oracle alternative.

As I get more from people, I will post.



1. https://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:7452431376537

Command Prompt, Inc.                  http://the.postgres.company/
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
Unless otherwise stated, opinions are my own.

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to