My preference with assign_mapper at this point is to say: Client.query.filter_by(sites=siteobj)
i.e. i dont think constantly adding methods to assignmapper is going to scale, as the chances of conflicts with existing user classes grows. im into hierarchies of names rather than huge straight down lists. On Apr 4, 2007, at 5:40 AM, Alexandre CONRAD wrote: > > Glauco wrote: > >> Alexandre CONRAD ha scritto: >> >>> Okay, thanks. Any idea if .filter_by() and other new "generative" >>> method >>> will be available in an assign_mapper object? >> >> Yes..it's available, the final object has identical property as a >> mapper > > Well, model.Client.filter_by(sites=siteobj) doesn't work for me... > > AttributeError: type object 'Client' has no attribute 'filter_by' > > Or am I misunderstanding how to use it ? > > Regards, > -- > Alexandre CONRAD > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
