Bug: comparison disable triggers

[Kuba]

When I compare trigger (using "compare user objects") which is disable and not exists in target db, PL\SQL Developer doesn't put "alter trigger ... disable" in generated script.

Kuba Kr

 

[Marco Kalter]

That is correct, the tool only compares the PL/SQL source of the trigger, not its status.

------------------
Marco Kalter
Allround Automations

 

[Kuba]

Originally posted by mkalter:
That is correct, the tool only compares the PL/SQL source of the trigger, not its status.

Well, I understand, but I think it should be an option in preferences window. It's very easy to forget about disable triggers and put them into target db as enable. Operations on tables could make a lot of problems than.

How about 'deferable' constraints? PL\SQL Developer can compare this constraint's status! If think it is similar situation.

Kuba Kr

 

[Marco Kalter]

I have added this to the list of enhancement requests. There are quite a few other compare options planned, so this could be added as well.

------------------
Marco Kalter
Allround Automations