On 12/6/05, Jonathan Daugherty <[EMAIL PROTECTED]> wrote: > That doesn't seem promote a clean separation of "table-level" > vs. "row-level" functionality.
What is the table-level functionality other than queries? Why not have a "get" or "query" member in the model class that does queries? Sure you could still do it from an instance, but I see that as a benefit. As in: polls = Poll.query.list(question__icontains='django') Or what if __new__ on Poll was defined so that you could search on that: polls = Poll(question__icontains='django') There are all sorts of ways you could do it that would be more intuitive.
