Comments
4 comments
-
Hello,
Just a note to anyone looking into this post -- we have a support ticket open currently and I'll post more here when I finish my investigation.
Thanks,
Evan -
From what I understand in the support ticket, this is a known bug:
(reference SC-4077) -
Bugs don't get fixed and you can't see the list of bugs either
-
Hello,
After updating our system, it does appear this is being discussed for a fix (SC-4077). I don't have a timeline, but it's definitely on the radar.
You're welcome to contact us periodically for updates on the bug. You can also check release notes for the list of bugs fixed each version: http://documentation.red-gate.com/displ ... ease+notes
Thanks,
Evan
Add comment
Please sign in to leave a comment.
I'm comparing two databases: The first is defined like this:
The second is defined like this:
When ignore nocheck is disabled (triple negative! meaning scrutinize nocheck), these compare as different (good!)
When ignore nocheck is enabled, these compare as the same, but that's not what I expected. The docs say disabled FKs are not ignored with this option and yet it seems to be ignored.
In my project, I really would like to ignore FK trustedness, but I really want to care about FK disabledness.