This is fixed by now and committed to SVN. Also please note that the cache is static, so you can use it efficiently accross different DataContexts (and inherited types). Let us know about performance.
Pascal. On Wed, Nov 19, 2008 at 23:25, Pascal Craponne <[EMAIL PROTECTED]> wrote: > Guess what? > It appears that you're right, the cache doesn't work. I'm working on a fix > right now. Let you know. > > > On Wed, Nov 19, 2008 at 18:44, Jimbo1982 <[EMAIL PROTECTED]> wrote: > >> >> So it looks like it is put in the cache but when it tries to find a >> match next time around it does not find one creates the expression >> again and puts it in the cache. >> >> The test for a match is done on the Expressions in the ExpressionChain >> by looking at their HashCode. Expression is a system Linq object so I >> can see how it generates it's hash code. >> >> Any idea's, I have the raw toStrings for each Expression which I can >> look at but they are quite intense. >> >> James >> >> >> > > > -- > Pascal. > > jabber/gtalk: [EMAIL PROTECTED] > msn: [EMAIL PROTECTED] > > -- Pascal. jabber/gtalk: [EMAIL PROTECTED] msn: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
