In a moment of maddness I've tried to improve performances of ExpressionEqualityComparer.Equals() by comparing Expression.ToString().
>From my tests, querycache retrieving was reduced to a 1%. After some test I've understood it was a bug, since Equals simply didn't worked for some expressions (making the collisions grow). This said, it's a so simple fix, that it should be in someway wrong, so please take a look at it! Giacomo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
