From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: contrib function naming, and upgrade issues |
Date: | 2009-03-22 13:29:45 |
Message-ID: | 937d27e10903220629p1ea32855qa5d9f80aceecc242@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Mar 22, 2009 at 11:54 AM, Andrew Gierth
<andrew(at)tao11(dot)riddles(dot)org(dot)uk> wrote:
> - want to be able to do INSTALL PACKAGE foo; without needing to
> mess with .sql files. This might default to looking for
> $libdir/foo.so, or there might be a mechanism to register packages
> globally or locally.
>
> - want to be able to do INSTALL PACKAGE foo VERSION 1; and get
> the version 1 API rather than whatever the latest is.
>
> - want to be able to do INSTALL PACKAGE foo SCHEMA bar; rather
> than having to edit some .sql file.
>
> - want to be able to do DROP PACKAGE foo;
>
> - want pg_dump to not output the definitions of any objects that
> belong to a package, but instead to output an INSTALL PACKAGE foo
> VERSION n SCHEMA x;
I think using PACKAGE is a bad idea as it'll confuse people used to
Oracle. MODULE perhaps?
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-03-22 13:48:02 | Re: contrib function naming, and upgrade issues |
Previous Message | Andrew Gierth | 2009-03-22 11:54:15 | Re: contrib function naming, and upgrade issues |