[sqlalchemy] Re: traversal order of ClauseVistor

2007-12-17 Thread Michael Bayer
On Dec 17, 2007, at 10:38 PM, Esceo wrote: Hi, I am just wondering about the traversal order of ClauseVistor, does it have to be in a set order? I am eagerloading lots (1000s) of relations, and query compilation take a long time, a profiling revealed that most of the time was spent in

[sqlalchemy] Re: traversal order of ClauseVistor

2007-12-17 Thread Esceo
Hi Michael, Thanks for the quick reply. What I am in fact doing is undefer all fields, eagerload all relations (and undefer the corresponding fields) for a corresponding model. (ended up being 9xx options altogether) And yes, I am on 0.3.11 (and probably is unable to move onto a 0.4 as I am

[sqlalchemy] Re: traversal order of ClauseVistor

2007-12-17 Thread Esceo
Hi, Seeing so many improvements and benefits, I might as well migrate to 0.4 Just few things I wanted to make sure before I start on that. Inside the 0.4 branch, 1) are we still generating anonymous labels with a width of 4 char ('anon_0fda') etc? 2) there is a bug inside 0.3's strategies

[sqlalchemy] Re: traversal order of ClauseVistor

2007-12-17 Thread Michael Bayer
On Dec 18, 2007, at 12:57 AM, Esceo wrote: Hi Michael, Thanks for the quick reply. What I am in fact doing is undefer all fields, eagerload all relations (and undefer the corresponding fields) for a corresponding model. (ended up being 9xx options altogether) And yes, I am on 0.3.11

[sqlalchemy] Re: traversal order of ClauseVistor

2007-12-17 Thread Esceo
no, 0.4 is almost a total rewrite of 0.3's internals.Of course its possible since its been done, but then youd just be left with... 0.4! Which you can just download. I'm not sure how extensive your elixir/SA hacks are but the Elixir project has also been improving and updating,

[sqlalchemy] Re: traversal order of ClauseVistor

2007-12-17 Thread Michael Bayer
On Dec 18, 2007, at 1:34 AM, Esceo wrote: Hi, Seeing so many improvements and benefits, I might as well migrate to 0.4 Just few things I wanted to make sure before I start on that. Inside the 0.4 branch, 1) are we still generating anonymous labels with a width of 4 char ('anon_0fda')