On 26 май, 20:50, Michael Bayer mike...@zzzcomputing.com wrote:
However, its quite easy to achieve. Just use this.
class LimitingQuery(Query):
def get(self, ident):
return Query.get(self.populate_existing(), ident)
def __iter__(self):
return
On May 27, 2009, at 4:25 AM, Denis S. Otkidach wrote:
On 26 май, 20:50, Michael Bayer mike...@zzzcomputing.com wrote:
However, its quite easy to achieve. Just use this.
class LimitingQuery(Query):
def get(self, ident):
return Query.get(self.populate_existing(), ident)
On 27 май, 18:22, Michael Bayer mike...@zzzcomputing.com wrote:
On May 27, 2009, at 4:25 AM, Denis S. Otkidach wrote:
class LimitingQuery(Query):
def get(self, ident):
return Query.get(self.populate_existing(), ident)
def __iter__(self):
return
On May 27, 2009, at 12:20 PM, Denis S. Otkidach wrote:
Probably I have to hack something to insure proper subqueries
construction.
uh yeah if subqueries are happening, that makes things more
complicated too. But the other DB tools you're comparing us
against probably have a lot less
On 26 май, 18:24, Michael Bayer mike...@zzzcomputing.com wrote:
Denis S. Otkidach wrote:
such ability in SQLAlchemy. There is a suggestion (
http://groups.google.com/group/sqlalchemy/browse_thread/thread/bcd10e...
) to provide custom query_cls. This probably worked a year ago, but
Denis S. Otkidach wrote:
Do you mean I have to create separate model definitions for public and
private parts of site? It doesn't seem sane to me. I've used such
filtering across all tables for over 10 years with other DB tools, and
it saved me a lot of work. Why not using it with SA?
I've
