What is identical in both files? The value in the Identity Columns or the
compound key (key1, Key2)?
Mit freundlichen Grüßen / Best regards
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jay
Sent: Donnerstag, 30. Januar 2020 22:40
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: sql table referential integrity
So i have table A (keyed by identity column), and index A (keyed by key1,
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?
Likewise if table A key value changes, table B key values change.
I know I am probably dreaming. I just don't want to go handle this stuff
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
As an Amazon Associate we earn from qualifying purchases.