I'm still analizing the question. QueryCache is busted. The only way to make it work is to do what was > originally done (make values part of the cached values), which results in > large memory use as every query variation is stored uniquely. >
If InputParameterExpression would Expression<Func<Expression, object>> containing a lambda able to find the parameter value in the expression, this would allow to store input parameters expressions in the select query and refilling parameters' values with the one provided current expression (without revisiting the tree). I really think that, since our sql generation process take much time, we should try this approach (which require adding an Expression<Func<Expression, object>> to many ExpressionDispatcher.Analizer method, I think...) Giacomo (PS I'm not sure to have been clear) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
