On Friday 01 June 2007 21:38:15 Michael Bayer wrote:
> On Jun 1, 2007, at 1:24 PM, Michael Bayer wrote:
> > and we can even bring back a modified version "auto-descend" in
> > that case:
> >
> > query(A).filter_by(C, lala=5)
> >
> > since above its not ambiguous.
>
> actually, scratch that.  C can be related to multiple times.   also
> its ambigious if you want "autojoin" to kick in or to use joins
> that are already within the from clause.
>
> so i modify my proposal to just whack auto-join period.
heh, if i remember how whole-heartly u defended this autodescend thing 
some months ago...

IMO u can have some configuration arg like autodescendjoin =False by 
default (or True to have it compatible with old code/lazy 
programmers) -- IF u want to somehow keep that unreliable 
traversal-guess at all.

Another herotic idea: look around the overriding userclass' __init__ 
method and why that is needed.
This seems to me to be somehow connected to assignmapper, it's again 
about autoguessing mappers/sessions.
IMO these notions (mapping, session-attaching, etc similar attaching 
of user-klas/obj to some DB/ORM-related thing) can be separated and 
have a possibility to make any combination of those, not just one 
hardcoded. e.g. the same way u can have now assignmapper vs not have 
one, u should have auto-mapper-compilation vs non-auto.

and more IMO, i think all these auto-guessing things in SA (and u have 
many,many of them, and u like them) are _okay_ as far as there is a 
way to disable them and require/specify all explicitly. Whether the 
default would be the (easy) autoguess or not, is irrelevant here.

did u get my point?

ciao
svil

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to