I have check ignore schema in object comparison, however, Triggers still show as changed due to schema. Is this a bug or intentional?
The triggers in my database show that the schema is there when looking at the create sql via sql developer.
I have checked to ignore schema's in object comparison.
The source control for oracle sql does not have the schema in it.
Consequently the tool shows all triggers that have the schema as changes.
Shouldn't these be avoided due to checking of schema in edit comparison options...?
Anonymous shared this idea