I'm wondering about what's needed to implement subqueries which are the next maior step in the development.
AFAIK, a maior refactoring could be required, since: - the BuilderContext is not a tree, so subqueries are mixed with the parents. - the ExpressionDispatcher analisis is done from the expression tree leafs up, and parts are instantly merged together with the outer query. (may be I'm wrong, please help me understand) So we would need to refactor and improve the ExpressionDispatcher analisis to not always be bottom up, but sometime considering the nodes contained in a specific node to identify subqueries and handling consiquently the BuilderContext. Moreover, what about BuilderContext.SelectExpressions? I saw a concept of scope but I could not understand how this work. 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 -~----------~----~----~----~------~----~------~--~---
