| From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
|---|---|
| To: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, Guillaume Perréal <perreal(at)lyon(dot)cemagref(dot)fr> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_dumpall and check constraints |
| Date: | 2000-07-01 00:25:14 |
| Message-ID: | 3.0.5.32.20000701102514.01faeec0@mail.rhyme.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
At 17:56 30/06/00 +0200, Jan Wieck wrote:
>
> For gods sake they don't have. And I'm uncertain that it
> should ever work.
Sorry...I'm the one to blame for the suggestion. My only defense is it was
late, and I was misled by the parser...never the less...
> How should a RESTRICT or ON
> DELETE CASCADE work in that scenario?
Perhaps as Check constraints on all tables in the view...for the most part
I would not expect complex views to be used in this way, but since this is
what the user would have to do anyway, why not do it for them?
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.C.N. 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2000-07-01 02:12:12 | Re: pg_dumpall and check constraints |
| Previous Message | Tom Lane | 2000-06-30 22:39:09 | Re: Trigger programming.. |