Is it possible to exclude from the delete policy some special custom tables not present in the original database schema?
Yes, not only for tables, but also for fields, indexes, and every other kind of database entity. You have to take care of naming the special entities you want to exclude from delete policy with one or more special prefixes. Then, in the project setting, you can define a list of prefixes used by DbUpdater to filter entities for delete policy. For example, we use the prefix “ERA_” or “CUSTOM_” when we need to allow the end user to create new tables/fields. Then, if the user defines a table named “CUSTOM_Employee” or a field named “ERA_LastName”, dbUpdater does not delete these entities even if the delete policy is enabled.
