Hi Atsushi! Yeah, I know why it fails. The problem was introduce when EntityRef lazy loading was implemented(http://groups.google.com/group/dblinq/browse_thread/thread/283191499b74199f)
Basically the EntityRef constructor is not implemented. The constructor has an IEnumerable parameter. The correct behaviour IMO would be to take the first element of such collection. I'll try to solve then and test the given sample in mono again. Regards your patches, they havebeen commited: http://code.google.com/p/dblinq2007/source/detail?r=905 On Wed, Oct 8, 2008 at 3:36 PM, Atsushi Eno <[EMAIL PROTECTED]> wrote: > > Ugh, looks like I made another mistake to include wrong source: > src/DbLinq/System.Data.Linq/EntitySet.cs, but should be > src/DbLinq/Data/Linq/EntitySet.cs. I fixed the issue and > reached EntityRef<T> .ctor(IEnumerable<T>): > http://monoport.com/37632 > > Atsushi Eno > > Atsushi Eno wrote: >> Oh sure: http://monoport.com/37630 >> >> Actually ExpressionMutatorExtensions.Evaluate() swallows the actual >> exception. I removed the catch and now I get: http://monoport.com/37631 >> >> (Am I seeing wrong exception? The SQL dump is now shorter.) >> >> Atsushi Eno >> >> >> Pablo Iñigo Blasco wrote: >>> On Wed, Oct 8, 2008 at 12:51 PM, Atsushi Eno <[EMAIL PROTECTED]> wrote: >>>> Atsushi Eno wrote: >>>>> Now It reached to another NotImplementedException which is >>>>> actually likely unimplemented yet. >>> Can you provide the stack trace? >>> >> >> >> > >> > > > > > -- Saludos. Pablo Iñigo Blasco . --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
