Beth Gatewood wrote:
>
> Chris/ Josh-
>
> OK-response to Chris below. Synopsis here....simply by creating a foreign
> key will not create an index. On large tables I SHOULD put a non-unique
> index on the foreign key (right?)
Right, because on DELETE or UPDATE to the primary key, the RI triggers have to check that this doesn't leave
orphaned references or do the required referential action (CASCADE). Sometimes this works faster with an index...
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #
