The order is not re-arranged for a pre-existing database.  If you are deploying to a table that already exists and new columns are added, you will see that they appear at the end of the natural structure instead of the order you may have them in the meta-data.  This is by design so that all pre-existing data is left intact.

No, it wasn't the matter. I always check for History before a new deploy.

This happens "every" time I launch deploy for the first time on an existing db. The second time DDT recreate the PK column, but maybe in a different order.

Gianpaolo Rocchi

Hi Gianpaolo.

Maybe you have deleted that column on the past for some reason and forgot to check the "Object Name History" node on the DDT treeview and delete that History item. Check if that is the case.

Hi,

some times, during a pkg deploing, DDT say "Column 'x' successfully dropped" as if the column haven't been touched since the previous deply on the same target db.

As a result, the db is left WITHOUT that pk column, and no error is reported.

Any idea?

Gianpaolo

Gianpaolo Rocchi