Compare User Objects - Dropped Triggers

[Rich Hull]

I'm relatively new to PSD, but so far, I really like it. I'm having some issue with the Compare User Objects feature where triggers are concerned. If a trigger in the source schema is dropped, isn't detecting that and so it's not generating the appropriate DROP command for the target. This appears to be related to the fact that PSD treats triggers differently than other dependent objects (such as constraints and indexes). You have to select triggers in the compare dialog, but you don't select constraints and indexes. The fact that you have to select a trigger in order for PSD to look at it is the problem. Although I can see the utility in being able to selectively compare triggers, it would be more useful (to me, anyway) to not have to mess with selecting triggers - just select the tables, and let PSD figure out what triggers to look at. In this situation, PSD could detect that a source table was different than a target table - because a trigger was dropped. Thanks.

 

[Marco Kalter]

The Compare User Objects tool will never drop objects from the target schema. It will only create missing objects and alter different objects. We will have an option to drop objects from the target schema in a future release though.

 

[Rich Hull]

That's what I'm looking for. Any idea of when the "future" is - Are we talking about version 8? -R.

 

[Marco Kalter]

Not 8.0.0, but maybe 8.0.x or otherwise 8.1.