AFAIK, such mapping can not change without a recompilation (and the application restart) so that chache could be a "simple" _thread_safe_ static Dictionary<Type, MetaModel> where the Type would be the DataContext.GetType() result.
Application can allow customers to add new columns to database tables in their databases after application is installed. To enable access to those columns from DbLinq child classes based on existing entity classes can be created at runtime using dynamic compiling. Those classes contain also linq attributes which need to be discovered at runtime. Old dblinq DataContext() instantiates very fast. It retrieves attributes only when they are actually required. In this case no cache was needed. Andrus. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
