When using the schema comparison feature, when Toad compares an XML Index it is not correct.
There are 2 scenarios;
1. The index does not already exist in the target
2. The index is different in the target
For scenario 1, is it possible that the resulting create statement in the sync script is able to define the actual XMLTYPE column name used?
For scenario 2, the resulting sync script statement where the XML index differs is an ALTER statement and should be a drop and create statement encompassing the above column name point, for the create statement.
