Unnecessary drop recreate of table when altering primary key sequence (4282900)

ENHANCEMENT REQUEST:
There are two tables having identical columns however, the primary indexes have different column order. Using Toad for DB2 v 4.7 to compare object then result of synchonization: drop table and recreate.
User expects the compare object wizard to generate alter statements for changing the PK constraint & index order.

STATUS:

Enhancement request ST 80069 has been submitted to Development for consideration in a future release of Toad for DB2.

WORKAROUND:

None