I can't seem to get the historical version to replace the current version  I press the button and the windows closes but the definition still remains the same.  I have tried it with a few objects and all of them act the same

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

Yes it just tables.  Thinking about the issue i think you reasoning is right as you could really mess up data.  You could give the user the choice and warn them that this could mess up the data.

In the first instance we'll add the message to make it clear why tables cannot be rolled back.  We'll then try and work a way by which we can allow the user to override this default behaviour.

Ideally it should overriding the default behaviour should be a little involved just to force users to make a conscious effort rather than accidentally clicking a button or two that ends up messing the data.

---

SQLDBcontrol Support

support@sqldbcontrol.com

Follow
the
white rabbit