On Nov 7, 2007, at 1:20 PM, svilen wrote:
> > ahha. so i am replacing one whole subexpr with somthing, and the > original subexpr is not traversed inside. > if i comment the stop_on.add(), it attempts to traverse the result > subexpr, not the original one. > i want the original to be traversed. Something like doing onExit > instead of current onEntry. > if its too hard, i can probably traverse it twice, once just marking , > 2nd time replaceing things? i'll try if youre replacing a subtree, why would you want to then traverse that part of the subtree which was replaced ? can you see why how i have it working now is reasonably straightforward ? perhaps a second call to ACP.traverse() should be called for those elements which were replaced. also r3754 fixes the issue that aliased selects, while being traversed, were not being copied properly. i still need to tweak the rules for aliases (alised tables, for example, remain immutable). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
