Tring to organize the work needed to make the QueryCache useful by allowing each InputParameterExpression to update it's own values from the updated expression, I encountered the ExpressionMutatorFactory and all the IMutableExpression implementations.
This is something I could not understand yet, about the DbLinq internals. Why we need them? I need to understand this, since to allow the closure to be updated via a delegate taking the expression (if not the ExpressionChain), I need to pass a lambda between the analizing method expressing how to reach the current analized expression from the initial one. Defining such a lambda should not be difficult by itself, but the ExpressionMutatorFactory make it harder. 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 -~----------~----~----~----~------~----~------~--~---
