Re: Proposal for SYNONYMS
От
Ragnar
Тема
Re: Proposal for SYNONYMS
Дата
Msg-id
1142032895.18656.194.camel@localhost.localdomain
Ответ на
Re: Proposal for SYNONYMS (Tom Lane)
Список
Дерево обсуждения
Re: Proposal for SYNONYMS "William ZHANG" <uniware@zedware.org>
Re: Proposal for SYNONYMS "Jonah H. Harris" <jonah.harris@gmail.com>
Re: Proposal for SYNONYMS Stephen Frost <sfrost@snowman.net>
Re: Proposal for SYNONYMS Stephan Szabo <sszabo@megazone.bigpanda.com>
Re: Proposal for SYNONYMS Stephen Frost <sfrost@snowman.net>
On fös, 2006-03-10 at 16:51 -0500, Tom Lane wrote:
> Kris Jurka writes:
> > One key difference would be that synonyms track schema updates, like
> > adding a column, to the referenced object that a view would not.
>
> That raises a fairly interesting point, actually. What would you expect
> to happen here:
>
> CREATE TABLE foo ...;
> CREATE SYNONYM bar FOR foo;
> CREATE VIEW v AS SELECT * FROM bar;
> DROP SYNONYM bar;
>
> With the implementations being proposed, v would effectively be stored
> as "SELECT * FROM foo" and thus would be unaffected by the DROP SYNONYM.
> Is that what people will expect? Is it what happens in Oracle?
At least on Oracle8, you could create a synonym on a
non-existing table, so if table FOO does not exist:
CREATE SYNONYM BAR FOR FOO; -- no error
SELECT * FROM BAR; -- error "synonym translation is no longuer valid"
CREATE TABLE FOO (a varchar2(10));
INSERT INTO FOO VALUES ('a');
SELECT * FROM BAR; -- no error
CREATE VIEW X AS SELECT * FROM BAR;
SELECT * FROM X; -- no error
DROP SYNONYM X; -- no error
SELECT * FROM BAR; -- error
gnari
В списке pgsql-hackers по дате отправления