Christopher Kings-Lynne wrote:
No it certainly won't warn you. You have _avoided_ the check entirely. That's why I was warning you...

I figured as much when I realized it was just a simple table update. I was thinking more of a DB2 style "set integrity" command.

If you wanted to be really careful, you could:

So I will be re-checking my own FKs. That's not really what I'd expect from a FK.

My problem with this really is that in my database it is hard to predict which inserts will be huge (and thus need FKs dissabled), so I would have to code it around all inserts. Instead I can code my own integirty logic and avoid using FKs all together.


Richard van den Berg, CISSP
Trust Factory B.V. |
Bazarstraat 44a    |
2518AK The Hague   |  Phone: +31 70 3620684
The Netherlands    |  Fax  : +31 70 3603009
   Have you visited our new DNA Portal?

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

Reply via email to