Hello world :-D Working on the lazy loading I've noticed some bugs in the DataMapper.
The worse is that it re-evaluate the mapping each time, even if mappings don't change. Fix this bug mean changing the IDataMapper interface too (which is used only in the DataContext and ExpressionDispatcher ). There are two ways: - Create a set of static thread safe dictionaries for mappings [1] - Create a set of static dictionaries filled with all possible results at application startup (toward an init metod? using a static constructor? any idea?) To choose we need to evaluate Mono support, thread safety and performance. I know this is a maior refactoring but I think it could dramatically improve performances. Giacomo [1] For a thread safe dictionary look at http://devplanet.com/blogs/brianr/archive/2008/09/26/thread-safe-dictionary-in-net.aspxbut note that I've not yet any experience about multi threads on .NET so it should be evaluated) On Tue, Apr 21, 2009 at 2:13 PM, Giacomo Tesio <[email protected]> wrote: > DataMapper.GetEntityRefAssociations() and > DataMapper.GetEntityRefAssociations() depend on Attribute based mapping. > > So XmlMappingSource could not work correctly on EntityRef and EntitySet > (neither on Mono nor on Microsoft.NET). > > > > 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 -~----------~----~----~----~------~----~------~--~---
