Re: question regarding REFERENCES and INHERITS
От | Stephan Szabo |
---|---|
Тема | Re: question regarding REFERENCES and INHERITS |
Дата | |
Msg-id | 20030331083401.D35743-100000@megazone23.bigpanda.com обсуждение исходный текст |
Ответ на | question regarding REFERENCES and INHERITS (Beatrice Yueksel <beatrice@msys.ch>) |
Список | pgsql-admin |
On Mon, 31 Mar 2003, Beatrice Yueksel wrote: > Hi, > I made some test with REFERENCES and INHERITS. > I know from the mailing list that : > "Referential integrity only applies to the named table and not > any child tables..." As a note, this phrase was intended to apply to the target referenced table (schiff_art in this case). > I have 3 tables: > art, > schiff_admin (for administration with rules, view, etc...) > schiff (inherits schiff_admin) > > There is one reference from schiff_admin to art. > The reference doesn't work in schiff. > > If I add a constraint: > > ALTER TABLE schiff_admin > ADD CONSTRAINT schiff_admin_fk_art > FOREIGN KEY(art) > REFERENCES > schiff_art (art) ON DELETE NO ACTION ; > > the reference works also in schiff. > > Why the reference is inherited after the "alter table" and not before? Because inheritance is wierd right now :) Seriously, the alter table is appearing to recurse the tree (as of the time the constraint is made), however create table inherits doesn't make the triggers. With pg_constraint in place, that might actually not be as hard now.
В списке pgsql-admin по дате отправления: