RE: [SQLObject] proxy attributes

[<jws...@ra...>]

>That seems much more doable.  You'd still have to do various traversals. 
>  Like, if you have a one-to-many relationship between A and B, and B 
>has an attribute "email", then you have to do a.b.email, instead of 
>simply a.email -- that's a separate feature entirely, and seems 

My immediate itch is many-to-one. I had not thought much about the
one-to-many case. I don't see any reason the existing scheme of returning
a list of objects would not work for me. It's hard to for me to 
evaluate my specific issue AND try to consider the One Correct Way.
I also labor under the disadvantage of near-complete ignorance of the
magic of metaclass programming. Enthusiasm and ignorance - A winning
combination!  

>Oh, and you have to fix _fromDatabase so that it detects foreign keys, 
>and can find classes based on table name.  But altogether a fairly 
>doable plan.

This is beginning to sound like traversal in Zope.