I've just tried this out now and I can only duplicate the behavior you describe with tables.

Can you confirm whether this behavior is specific to just tables or are you also experiencing this on other object types?

When we implemented support for tables we decided against allowing table changes being rolled back - primarily because a table consists of more than just a schema and we were concerned that rolling back could cause the loss of data. In theory a message should pop up and explain that this is the case so we'll aim to fix that.

That said, if there is a need to be able to roll back table changes it won't be difficult to allow for table changes to be rolled back because the code is already in place (we just don't call it). We would just have to precede it with a big warning message about potential data loss.

---

SQLDBcontrol Support

support@sqldbcontrol.com