I've just summitted 3 test for tracking the implementation of this two features. http://code.google.com/p/dblinq2007/source/detail?r=1043
Yesterday I've located the EntityTracker inside the DataContext. Here my plan for changes: - Create a IEntityTraker interface. - Make EntityTraker implement IEntityTraker - Create a DisabledEntityTraker class, implementing IEntityTraker. - Create a private readonly property DataContext.EntityTraker - Make all references pointing to the entityTraker field, point to the new property - In the getter of DataContext.EntityTraker populate the entityTraker field according to the ObjectTrakingEnable value - When setting ObjectTrakingEnable, throws the proper exception if the entityTraker field is not null. All this work assume that the EntityTraker is the only cache of entities in the system, is this right? Moreover, I've no idea wher to look for disable deferred loading (lazy loading). Please let me know what you think about this... Giacomo On Sun, Apr 5, 2009 at 10:35 PM, Giacomo Tesio <[email protected]> wrote: > Hi... unfortunately I've found no time to take a better look to DbLinq > object tracking. > > Where are located the caches that should be disabled when > ObjectTrackingEnable is false? > > > Giacomo > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
