Yes, our DB is split up into multiple schemas (Core, Security, moduleA, moduleB,...)
For FDA compliance, we added audit trailing and have chosen to have 1 audittable per table, in audit schema'ss (AuditCore, AuditSecurity,...). The auditing is handled in an override of OnSaveEntityComplete of the DataAccessAdapter (only a few lines of code, and since we don't to Deletes, it's the simplest approach). The implementation needs us to have an IAuditable interface on all entities (except of course on the Audit-entities themselves)
Different schema's result into different groups per default in the designer. It would be very handy to be able to define the IAuditable interfaces at the group level.
The options now are :
- at project level : not good, our audit-entities then also are IAuditable
- at entity level : has to be added for hundreds of entities, a boring and error-prone work
As a matter of fact, what is the intention of splitting up in groups in the designer ? I don't see any benefits (no other namespaces, no "customization" at group level) except for the visualization in the designer (which is already nice of course
Kind regards,
Sven.