How can we help you today? How can we help you today?

Enabled/disabled triggers are ignored.

Some time ago, I reported a bug: tables are considered equal when a trigger on one side is enabled, but disabled on the other one. Unfortunately this still holds true for version 8 (Beta).

When you synchronize a new but disabled trigger to the destination db, this trigger is created but set to enabled, which is a very dangerous behaviour.

Interestingly SQLCompare behaves correctly when comparing check constraints: tables with enabled/disabled constraints are considered different.

When I reported this bug (more than a year back), I was told that this will be changed in the next version (which was 7). Obviously this bug now survives the 2nd major version.
franz
0

Comments

1 comment

Sort by
  • David Atkinson
    I've checked your bug report (reference: SC-3996) and it's still on the list of candidates to be resolved for v8.0. Of course there is long list so we can't make any promises, but to let you know that all hope isn't yet lost!

    Regards,

    David Atkinson
    Red Gate Software
    David Atkinson
    0

Add comment

Please sign in to leave a comment.