By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,933 Members | 1,716 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,933 IT Pros & Developers. It's quick & easy.

Foriegn Key constraints not enforced when using rules

P: n/a
Bob
Hi,

Does anyone know why forgein key constraints are not enforced when
updateing multiple tables using a combination of views and rules?

This doesn't seem to be a major problem as I can specify the columns
in question as not null and this will produce an ExecInsert error if
the data is not present in my insert.

However, it seems to me that it would be better to be able to rely on
my foreign key constraints.

Why are they ignored?

Thanks in advance,
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Bob
bo********@hotmail.com (Bob) wrote in message news:<b5*************************@posting.google.c om>...
Hi,

Does anyone know why forgein key constraints are not enforced when
updateing multiple tables using a combination of views and rules?

This doesn't seem to be a major problem as I can specify the columns
in question as not null and this will produce an ExecInsert error if
the data is not present in my insert.

However, it seems to me that it would be better to be able to rely on
my foreign key constraints.

Why are they ignored?

Thanks in advance,


Please ignore this - I've realised that my foriegn keys are behaving
just as they should be. NULLs are handled differently.

Thanks,
Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.