Bonjour Pascal, Pascal Craponne wrote: > in theory, DbLinq should only use its own EntitySet<> and EntityRef<>. > If a non-DbLinq class is present somewhere in test code, this is a > mistake. DbLinq probably still supports in the core a bit of MS > EntitySet and Ref to keep a bit of compatibility, but we may also drop > those parts in the future.
OK, I've found the code that created System.Data.Linq.EntitySet<T>. It was Northwind.cs :/ Probably it is automatically generated by DBMetal? Actually when I replace them with DbLinq.Data.Linq.EntitySet, it seems to get into some infinite loop. I'll dig it in depth later. > Regarding eager loading, nothing appears to be in progress (I haven't > heard from Pablo for a while, by the way). I can develop my architecture > idea about this if you are interested. That'd be great :) (And I am also not sure if Pablo is still alive.) > Anyway, the following remaining tasks are related and should be solved > together: > - complex subexpressions > - eager and lazy loading (lazy loading currently works, but I'm not sure > it fits in the global idea) Right, they are tied together. > However I haven't been giving DbLinq much time last month (apparently > I'm not the only one), so all of this is in standby mode. Yep, while I haven't seriously worked on dblinq until this month ;-) Atsushi Eno --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
