The exception means that the expression could not be translated correctly, so the cache doesn't help here. Anyway, one problem at a time. Regarding your cache problem, apparently, something tells the expression comparer that the two expressions are different. I suspect that this is a variable problem (a variable is passed as parameter), but can you place breakpoints on every line with "return false" in ExpressionEqualityComparer and see where it fails?
Pascal. jabber/gtalk: [EMAIL PROTECTED] msn: [EMAIL PROTECTED] On Tue, Dec 2, 2008 at 15:37, Jimbo1982 <[EMAIL PROTECTED]> wrote: > > Yes even when I do a simple select against a new table with two > Varchar2 columns I still got the exceptions. > > So more specifically if the caching works or does not I always get the > exceptions (obviously only on the first call if caching works). > > James > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
