-Original Message-
From: sqlalchemy@googlegroups.com
[mailto:sqlalch...@googlegroups.com] On Behalf Of Chris Withers
Sent: 01 July 2010 19:17
To: sqlalchemy@googlegroups.com
Subject: [sqlalchemy] models in different packages, often
declaratively defined
Hi All,
Suppose I
Hi there,
The documentation for the undefer() method seems to indicate that it
should be able to accept multiple positional arguments for keys,
however trying this results in an error. I wanted to post this here to
check I'm right in thinking this before I file a ticket. The docs give
the
Michael Bayer wrote:
I'd welcome any patches in this regard since I don't usually deal with the
mixin feature.
fine, how about Chris works up the unit test for it:
Done and pushed back to tip with the fix.
cheers,
Chris
--
You received this message because you are subscribed to the
undefer accepts *args so that you could define a path from the parent object of
the query down to the child:
query(Parent).options(undefer(Parent.child, Child.subchild,
Subchild.someattribute))
The public docs currently don't really explain this detail, unless you were to
guess that undefer()
Michael, thanks for your help.
sorry, I dont have any context here. Are you looking for this ?
For some reason I can't reply to this thread on google news, yet I can
do with gmane newsgroups :-/
engine = create_engine('...')
Integer().get_dbapi_type(engine.dialect.dbapi) ?
that will give
On Jul 2, 2010, at 6:10 AM, Meitham wrote:
Michael, thanks for your help.
sorry, I dont have any context here. Are you looking for this ?
For some reason I can't reply to this thread on google news, yet I can
do with gmane newsgroups :-/
engine = create_engine('...')
On Jul 1, 2010, at 8:24 PM, Michael Bayer wrote:
The Column object contains a sort key when constructed, against a single
global value, that is used as a sort key when the Table is generated. This
is to get around the fact that the attribute dictionary of the declarative
class is
