From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | josh(at)agliodbs(dot)com |
Cc: | rmm(at)sqlisor(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Oracle Style packages on postgres |
Date: | 2005-05-09 19:33:24 |
Message-ID: | 690.1115667204@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> What I read in this thread is that the only truly missing feature is
>> package variables (ie, session-local variables); is that an accurate
>> statement? If so, it would seem simplest to add such a feature to
>> plpgsql and be done with it. Several people already pointed out that
>> most of the other PLs support that feature today.
> Also initialization, namespacing, and security. The ability to "package"
> bunches of functions, and only allow their calling in the context of a
> package, is quite valuable in installations which support 1,000's of
> procedures.
This is exactly the sort of argumentation that got the last proposal
shot down ;-). I see no reason that you can't do the namespacing and
security as well or better using the existing (and more standard) schema
feature. If there's something there that's not covered, what is it?
(The initialization bit goes along with the variables, AFAICS.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2005-05-09 19:39:38 | Re: Inline PL/pgSQL |
Previous Message | Josh Berkus | 2005-05-09 19:30:40 | Re: Oracle Style packages on postgres |