This content has been marked as final. Show 7 replies
I think that this is probably a bug and we are researching it further. Assuming that the dropped column is the only difference, the "Ignore Table Column Position" option should result in generation of Alter Table Drop Column syntax rather than Drop/Create Table Syntax. I expect that you have the "Ignore Table Column Position" option checked because it is the default.
Thanks for looking into this. Yes, I tried with the "Ignore Table Column Position" both checked and unchecked and it didn't seem to matter. All that was changed on the table was 2 columns were dropped and neither had any indexes or FKs or anything else associated with them -- just simple drops. Maybe it was because more than one column was dropped?
I have filed a bug on the problem and a fix is being developed. Thanks for your feedback and sorry for the inconvenience.
No problem, the fixes turned out to be pretty easy. Thanks for filing bugs. Overall the tool works really well and is easy to use.
Is there by any chance a patch for this already?
The bug that Joyce logged in turn generated a bug against the Change Management component of Oracle Enterprise Manager. That has been fixed, but for a future version of the database only, and with the feasibility of backporting the fix to an earlier version marked as "No".
So, with product dependencies in the mix, it is a bit more complicated than a simple patch to SQL Developer.
SQL Developer Team
Ok thanks :)