Michael Bayer wrote: > My preference with assign_mapper at this point is to say: > > Client.query.filter_by(sites=siteobj)
For the mailing list's archives correctness: 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. I understand. I also think that having it in the query() is a good practice. Then maybe the methods directly accessible from Client.xxxxx() should be set as deprecated ? Regards, -- Alexandre CONRAD > 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 >> >> >> > > > > > > > --------------------------------------------------------------------------------------------------- > Texte inséré par Platinum 2007: > > S'il s'agit d'un mail indésirable (SPAM), cliquez sur le lien suivant pour > le reclasser : http://127.0.0.1:6083/Panda?ID=pav_33314&SPAM=true > --------------------------------------------------------------------------------------------------- > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
