I was testing a bit more with DbLinq and MySql, and noticed some
endless loops during a LINQ query that used "where x == 1 && y == 2".
While debugging, the problem was traced down to where a unique alias
is assigned to an expression. It also appeared some queries were not
being cached properly while building the expression. Since the
previous fix resolved the issue of the long delay while building
expressions, it looks like you may be able to actually take out the
caching of expressions altogether. I tested by removing the expression
builder caching feature and adding a fix for the query above and this
appears to work well. I've created a patch with these changes so you
can take a look and see how it works on your end. You can download it
at the second SVN Patch link at http://www.primaryobjects.com/CMS/Article99.aspx
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
