| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Rod Taylor" <rbt(at)zort(dot)ca>, "Hackers List" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_constraint |
| Date: | 2002-04-26 07:34:12 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOIEEKCCAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> For tracking of Foreign Keys, Check constraints, and maybe NULL / NOT
> NULL (specific type of check constraint) I intend to create (as per
> suggestion) pg_constraint.
Hmmm...I don't see the need at all for NOT NULL constraint tracking. The
spec doesn't seem to require it and we do not have names for them anyway.
Even if they were given names, it'd be pointless, as there's only one per
column.
Primary keys and unique keys are SQL constraints - are you going to bother
tracking them as well or leave them in the current format? Maybe you could
do it with a view or something.
Why not just create a pg_references table and leave pg_relcheck as is?
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shad | 2002-04-26 08:37:50 | PSQL \x \l command issues |
| Previous Message | Francois Suter | 2002-04-26 06:52:33 | Re: pid gets overwritten in OSX |