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 [email protected]
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
-~----------~----~----~----~------~----~------~--~---
