This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I have a set of classes for which I would want the ChangeTracker to be always turned on. I was considering enabling it in a base class constructor. My question is whether this will add overhead to the object load (or other operations). Otherwise I would have to add a call to enable tracking in multiple places in my app. Any advice on this? Thanks! |
|
|
There isn't any overhead for initial hydration of entities as we perform field assignment rather than property assignment where this gets triggered so this sounds fine but I would certainly encourage you to benchmark things to make sure you are happy with the extra memory usage that this feature can incur, particularly if you are making an indeterminate number of modifications (e.g. entirely driven by user activity).
|
|