| From: | Decibel! <decibel(at)decibel(dot)org> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Table inheritance surprise |
| Date: | 2008-05-09 13:55:34 |
| Message-ID: | 8CE09ABF-3462-4EA5-A7E2-ABD06BB24FC9@decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On May 7, 2008, at 4:52 PM, David Fetter wrote:
> When I do CREATE TABLE foo(LIKE bar INCLUDING CONSTRAINTS), it doesn't
> include foreign key constraints (8.3.1). I believe this is surprising
> behavior, but maybe not a bug, so I'd like to propose another bit of
> syntactic sugar, namely
>
> LIKE [INCLUDING FOREIGN KEYS]
>
> which would do what it looks like it does.
It's surprising to me that INCLUDING CONSTRAINTS doesn't include FK
constraints... is there a reason not to? Perhaps we should just
change INCLUDING CONSTRAINTS to do that...
--
Decibel!, aka Jim C. Nasby, Database Architect decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-05-09 14:01:44 | Re: constraint exclusion analysis caching |
| Previous Message | David Fetter | 2008-05-09 13:33:04 | Re: Auto-updated fields |