From: | "Nick Barr" <nicky(at)chuckie(dot)co(dot)uk> |
---|---|
To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Rory Campbell-Lange" <rory(at)campbell-lange(dot)net> |
Cc: | "Postgresql General List" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Naive schema questions |
Date: | 2004-05-27 12:32:14 |
Message-ID: | 000f01c443e6$a59c00a0$3202a8c0@webbased10 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
----- Original Message -----
From: "Peter Eisentraut" <peter_e(at)gmx(dot)net>
To: "Rory Campbell-Lange" <rory(at)campbell-lange(dot)net>
Cc: "Postgresql General List" <pgsql-general(at)postgresql(dot)org>
Sent: Thursday, May 27, 2004 1:10 PM
Subject: Re: [GENERAL] Naive schema questions
> Am Donnerstag, 27. Mai 2004 13:15 schrieb Rory Campbell-Lange:
> > I imagined schemas might allow me to globally update functions across a
> > database hosting many schemas with the same structure.
>
> Put your data tables in separate schemas, put the functions in yet another
> schema, and then when you connect set the schema search path to
"dataschema,
> functionschema" (or maybe vice versa).
Or when you make the calls in the web app use the following:
SELECT function_schema.function1(arg1, arg2);
instead of just:
SELECT function1(arg1, arg2);
But like Peter said have a schema per client/"instance" of your database.
Nick
From | Date | Subject | |
---|---|---|---|
Next Message | rama | 2004-05-27 13:28:08 | statement level triggers in PostgreSQL , anybody?? |
Previous Message | Jan Wieck | 2004-05-27 12:18:14 | Re: Naive schema questions |