×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
<Jay>
So i have table A (keyed by identity column), and index A (keyed by key1,
key2).
I have table B (keyed by identity column) and index B (keyed by key1, key2
- same defined keys as in index A)
table B is really just an "additional information" table for the rows and
keys defined in table A.
How can I apply some kind of referential integrity over table B to allow
table B keyed rows to be deleted if table A similar keyed rows are
deleted?
<snip>
... this could be done by a referential constraint - if the matching key of
table A is unique! Better design would be if the matching key is primary key
of A.
</snip>
Likewise if table A key value changes, table B key values change.
<snip>
this is impossible with referential constraints (not allowing changes of the
parent key) and in contradiction to the concept of sql at all: a primary key
must not change!!!
</snip>
I know I am probably dreaming.
</Jay>
... seems to be a nightmare to me!
Dieter
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
