On Wed, May 10, 2006 at 01:14:40AM +0300, Gambit wrote: > Hey Sandro, > > Ooh, that's what you meant by doubled rows. > > You're just asking for users where the mail address matches the criteria. If > you want to limit the mail entries then, for a given user, performing an > additional select on the mail table backwards (i.e. supplying the limiting > userid, or userids) is one possible way.
I guess you are kidding, here... > The issue here is since you're asking for Users, you're going to get all > the Users that match the criteria. There isn't any logic in place to then > limit your exposure to properties (and, I'd think, would be difficult to I don't think I understand what you mean by "limit your exposure to properties" > implement, due to the need to then track in each object all the various > conditions it was found under) of the User objects you find. > > If you want a straight list, then maybe stick with straight SQL? I don't want a list, I want instances I can modify! But I hope this is just a bug not a "feature"!... sandro -- Sandro Dentella *:-) e-mail: [EMAIL PROTECTED] http://www.tksql.org TkSQL Home page - My GPL work ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
