From: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
---|---|
To: | Brendan Jurd <direvus(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Shorthand for foreign key indices |
Date: | 2005-05-08 17:10:54 |
Message-ID: | 20050508171054.GC88920@decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, May 09, 2005 at 02:05:14AM +1000, Brendan Jurd wrote:
> CREATE TABLE foo (
> foo int NOT NULL REFERENCES bar INDEX
> );
>
> ... would be marvellous
I agree that it would be handy. Another possibility is throwing a NOTICE
or even WARNING if you create a foreign key that isn't covered by an
index.
> My apologies if this has been answered before, but a search of the
> -general mailing list was not fruitful.
FYI, often times new ideas are only discussed on -hackers, so you should
search there as well.
--
Jim C. Nasby, Database Consultant decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2005-05-09 03:36:40 | Re: [HACKERS] Invalid unicode in COPY problem |
Previous Message | Tom Lane | 2005-05-08 16:38:01 | Re: SQL History |