From: | <jjeffman(at)cpovo(dot)net> |
---|---|
To: | <jjeffman(at)cpovo(dot)net> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: table synonyms |
Date: | 2005-05-24 02:21:29 |
Message-ID: | 000001c56007$4b101570$0793f8c8@pegasus |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
So the search_path can not substitute the Oracle synonyms function which
in a single way allow us to write generic queries for an application no
matter the schema which is being used.
I can not find a solution on this matter in PostgreSQL.
I hope anybody can help me on this subject. The problem is not to find a
substitute for the Oracle synonyms, but a way to write queries which,
reliably, can be used no matter the schema which owns the tables.
Jayme
----- Original Message -----
From: Martijn van Oosterhout
To: jjeffman(at)cpovo(dot)net
Sent: 23-May-2005 12:53:30 -0300
CC: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] table synonyms
On Mon, May 23, 2005 at 09:07:08AM -0300,
It takes the first one.
There is no explicit relationship between users and schemas, however
many installations have the search_path default to "$user, public"
which is magically substituted on connection. You are ofcourse free to
alter search_path whenever you want. Any table can always be referred
to by its full name...
Hope this helps,
--
Martijn van Oosterhout http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is
a
> tool for doing 5% of the work and then sitting around waiting for
someone
> else to do the other 95% so you can sue them.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-05-24 04:12:35 | Re: pg_dump in a production environment |
Previous Message | Scott Marlowe | 2005-05-23 22:09:58 | Re: pg_dump in a production environment |