maybe keep only _one_ method which gives a fullblown Query() object, which then can be used as one wish?
On Friday 01 June 2007 06:47:01 Michael Bayer wrote: > heres the question. Query gets 10 new methods one day. do we then > add 10 methods to assign_mapper() ? must the user class be a total > clone of Query ? assign_mapper just bugs me for this reason. > hence i like entity.query() better. im not sure which one youre > saying you prefer ? > > On May 31, 5:46 pm, "Mike Orr" <[EMAIL PROTECTED]> wrote: > > What are future plans for the assign_mapper query methods? > > > > MyClass.select(...) > > -- works great. A clear advantage for assign_mapper over the > > regular mapper. > > > > MyClass.filter(...) > > -- doesn't exist. > > > > MyClass.query().filter(...) > > -- works but is undocumented and requires a convoluted > > monkeypatch in the source. Not so clear an advantage over the > > regular mapper because it's so verbose. > > > > The third is the one I've found most useful. That way I can have > > functions that return a Query, and the caller can call .select(), > > .select(offset=,limit=), or .count() as they wish. > > > > -- > > Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
