| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: contrib idea |
| Date: | 2001-12-24 02:49:57 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOEEOJCAAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > > * Check to see if the child row exists (no action)
> > > * Delete the child row (cascade delete)
> > > * Update the child row (cascade update)
> > >
> > > All of which will benefit from an index...
> >
> > OK, then perhaps we should be creating an index automatically? Folks?
>
> The index is only useful where you actually have an on delete or on update
> clause.
Hmm...not necessarily true. A default 'no action' foreign key still needs
to prevent the parent key from being deleted if the child exists. This
requires that postgres do a search of the child table.
> I don't think we want to conditionally create an index. That would
> bee too confusing. A contrib, to find "suggested" indexes seems fine.
That's what I suggested.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-12-24 03:27:13 | Re: Thoughts on the location of configuration files |
| Previous Message | Bear Giles | 2001-12-24 02:46:31 | Announcement: libpkixpq 0.1 released |