March 7, 2012 at 7:34 am
I believe so, but the only way to know for sure is to test it.
If your primary key is subject to change in the way you mention, you may consider using a surrogate key as your primary key - an identity column, for example.
John
March 7, 2012 at 7:40 am
No, I'm afraid that a surrogate key wouldn't solve the problem. I'll test the first option and tell you the results 🙂
March 7, 2012 at 7:58 am
The update will fail I believe - as the non-cascading FK would be violated.
a.penasco (3/7/2012)
No, I'm afraid that a surrogate key wouldn't solve the problem.
Why not? Seems a good solution to me & should avoid the need for any cascading actions.
Also, Ms Sherbatsky is far too pretty to be updated or deleted 😀
March 7, 2012 at 8:27 am
A surrogate key will mean changing all the tables fields that refer to Users, which is a suicide duty. There's too many data and too many tables. But I'll take that in mind for future challenges.
You've been so helpful! I wish you a night with Ms. Sherbatsky LOL
Viewing 4 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply