From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | constraint defaults still print |
Date: | 2003-01-18 20:54:10 |
Message-ID: | 200301182054.h0IKsAv21191@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | D. Hageman | 2003-01-18 22:51:12 | Namespace/Table Visibility Behavior Issues |
Previous Message | Tom Lane | 2003-01-18 16:13:26 | Re: Can we revisit the thought of PostgreSQL 7.2.4? |