Joris,

There are a couple of ways a table can be deleted from the channel:

1. Table is dropped in the database. You can configure action AdaptDDL to automatically delete the table from the channel.
2. Manual deletion: you used to replicate the table, but you no longer want to do this.

I assume you ask about the second scenario.

Please note that HVR separates design and run time. The design time is what you look at in the repository. At any time you can propagate your current design to runtime with the activate step. Activate always considers the current state of the channel definition.

You may be making a number of changes to your channel definition. And as part of this you may delete a table. If we automated the activation following the deletion of the table then you may end up with a channel that used to work and no longer does (since you may be in the middle of making changes when deleting the table).

I suppose we could ask the user whether they want the removal of the table to be immediate. At that point we could create a control to skip this table. However this is also not ideal because then when do we remove the control?

You might say we remove the control after activate, but let's say you activate an hour later but integrate latency is a day. You then have captured changes without HVR knowing how to integrate them. This currently generates errors (maybe we should address this first). Of course alternatively we could not remove the control but what if you change your mind and want to add the table again? We then must remove the control.

Bottom line a lot of these things can be built but there are corner cases that make this a complicated scenario. For now we'll leave the behavior the way it is.

Thank you,
Mark.