Subject | Re: [Firebird-Architect] Multi Connection meta data update |
---|---|
Author | Ann W. Harrison |
Post date | 2004-11-09T16:48:28Z |
At 06:10 AM 11/7/2004, Dmitry Yemanov wrote:
the referenced table and the referencing table, but only the referencing
table gets a new index. If an existing classic connection has a compiled
request that deletes rows from the referenced table, that request will
not be invalidated by the creation of a foreign key constraint, and can
cause inconsistencies.
Regards,
Ann
>They are propagated. You may create an usual index in a multi-connectionIf you create a foreign key relationship, you put constraints on both
>scenario in CS without problems, don't you? How do FK indices differ?
the referenced table and the referencing table, but only the referencing
table gets a new index. If an existing classic connection has a compiled
request that deletes rows from the referenced table, that request will
not be invalidated by the creation of a foreign key constraint, and can
cause inconsistencies.
Regards,
Ann