Notes in-line.
--
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk
The educated person is not the person
who can answer the questions, but the
person who can question the answers -- T. Schick Jr
One-day tutorials:
http://www.jlcomp.demon.co.uk/tutorial.html
____Belgium__November (EOUG event - "Troubleshooting")
____UK_______December (UKOUG conference - "CBO")
Three-day seminar:
see http://www.jlcomp.demon.co.uk/seminar.html
____UK___November
The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html
"Domenic G." <domenicg_at_hotmail.com> wrote in message
news:c7e08a19.0311090751.78ec77be_at_posting.google.com...
>
> The index should be there unless the parent table is read only.
>
Too extreme - the table can be updated provided
you don't update the primary key (or delete rows,
as you pointed out), or any column that has been
added to the index that supports the primary key.
> Dom.
>
>
> "Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote in message
news:<bol9d6$gq3$1$8300dec7_at_news.demon.co.uk>...
> > Your comment needs a little clarification.
> >
> > It is a bad idea to create an index on a
> > set of columns simply because that set
> > of columns represents a foreign key constraint.
> >
> > Indexes should be created if, and only if,
> > they add value. Indexes "on foreign keys"
> > do not necessarily add value.
> >
Received on Sun Nov 09 2003 - 12:06:51 CST
