From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: constraint defaults still print |
Date: | 2003-01-19 02:09:13 |
Message-ID: | 20030119100852.Y12036-100000@houston.familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I vote for not showing 'NO ACTION', so long as it's the SQL standard
default...
Chris
On Sat, 18 Jan 2003, Bruce Momjian wrote:
> Remember how we made DEFERRABLE/DEFERRED not print if the constraint was
> the default. Shouldn't we do the same for MATCH and ON UPDATE/ON DELETE
> sections of the constraint in pg_get_constraintdef()?
>
> Doing \d I see:
>
> test=> \d sales
> Table "public.sales"
> Column | Type | Modifiers
> -------------------+---------+-----------
> product_id | integer | not null
> store_id | integer | not null
> quantity_sold | integer | not null
> date_time_of_sale | date | not null
> Foreign Key constraints: $1 FOREIGN KEY (product_id) REFERENCES
> products(product_id) ON UPDATE NO ACTION ON DELETE NO ACTION,
> $2 FOREIGN KEY (store_id) REFERENCES
> stores(store_id) ON UPDATE NO ACTION ON DELETE NO ACTION
>
> If NO ACTION is the default, is there a need to print them? This would
> also shorten pg_dump output.
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
> + If your life is a hard drive, | 13 Roberts Road
> + Christ can be your backup. | Newtown Square, Pennsylvania 19073
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>
From | Date | Subject | |
---|---|---|---|
Next Message | Lamar Owen | 2003-01-19 02:40:34 | Re: Can we revisit the thought of PostgreSQL 7.2.4? |
Previous Message | D. Hageman | 2003-01-18 22:51:12 | Namespace/Table Visibility Behavior Issues |