Re: Shorthand for foreign key indices - Mailing list pgsql-general

From Brendan Jurd
Subject Re: Shorthand for foreign key indices
Date
Msg-id 37ed240d05051011134494ab83@mail.gmail.com
Whole thread Raw
In response to Re: Shorthand for foreign key indices  ("Jim C. Nasby" <decibel@decibel.org>)
List pgsql-general
On 5/9/05, Jim C. Nasby <decibel@decibel.org> wrote:
> 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.
>

Good idea.  WARNING might be going too far though.  NOTICE sounds just
about right to me.

> > 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.

Well, so far nobody's raised any objections.

Would it be worthwhile to repost this on -hackers?  I did do a search
on the mailing list archives for that list as well, and didn't come up
with anything that bore directly on this discussion.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PERFORM] "Hash index" vs. "b-tree index" (PostgreSQL
Next
From: "Leif B. Kristensen"
Date:
Subject: Re: Loading a list of SQL scripts with relative paths