Thread: PL/SQL packages

Hi,
 in our TODO is the item: "Add PL/PgSQL packages".
 I thought about  it and for example Oracle's CREATE  PACKAGE / PACKAGEBODY seems  really interesting and modular. IMHO
it's interesting itemin PostgreSQL TODO, but I think  there a is small collision between theschemas and possible
packagecontents referencing: SELECT xyz.funcname();        ^^^Is it some  function in schema 'xyz' or some  function in
package'xyz'in the current schema? Or is needful check both alternatives?Do you have any experience with it?
 
   Karel
-- Karel Zak  <zakkr@zf.jcu.cz>http://home.zf.jcu.cz/~zakkr/

Karel Zak writes:

>   in our TODO is the item: "Add PL/PgSQL packages".

I think the interesting part are the package-global variables.  The
name hierarchy seems completely redundant with schemas.

-- 
Peter Eisentraut   peter_e@gmx.net

On Fri, Nov 28, 2003 at 02:35:11PM +0100, Peter Eisentraut wrote:
> Karel Zak writes:
> 
> >   in our TODO is the item: "Add PL/PgSQL packages".
> 
> I think the interesting part are the package-global variables.  The
> name hierarchy seems completely redundant with schemas.
Agree, but there is more advantage than package-global variablesonly. The Oracle PACKAGE:   - package is interface
definitiononly and the real functions are   defined in PACKAGE BODY, it allows you change internal logic, but
interfaceis still same. 
 
   - package-global cursors
   - package-global variables
   - ??
Maybe  PACKAGE can  be in  PostgreSQL implemented  as special  a littleextended schema (like sequence are  special
table)and we needn't thinkabout something new.
 
   Karel

-- Karel Zak  <zakkr@zf.jcu.cz>http://home.zf.jcu.cz/~zakkr/