Re: Shorthand for foreign key indices

From: Brendan Jurd <direvus(at)gmail(dot)com>
To: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Shorthand for foreign key indices
Date: 2005-05-10 18:13:48
Message-ID: 37ed240d05051011134494ab83@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 5/9/05, Jim C. Nasby <decibel(at)decibel(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Leif B. Kristensen 2005-05-10 18:58:37 Re: Loading a list of SQL scripts with relative paths
Previous Message Mischa Sandberg 2005-05-10 18:12:45 Re: [GENERAL] "Hash index" vs. "b-tree index" (PostgreSQL