Feature #4054
only track specific tables in dirty database
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
version:
History
#1 Updated by Eric Faulhaber about 5 years ago
The idea is to improve performance of the persistence layer by only tracking certain tables within the dirty database implementation, which we know need this special support. This would be done by conversion hint, which would add an annotation to the DMO implementation class.
I have to look back through the dirty database implementation, however, because I have a nagging feeling that we have one or more dependencies on this feature at the moment, which would be broken by this approach.