On 13/09/10 18:21, Michael Bayer wrote:
On Sep 13, 2010, at 12:26 PM, Jon Siddle wrote:
This relationship is satisfied as you request it, and it works by looking in the current
Session's identity map for the primary key stored by the many-to-one. The operation
falls under the realm
with its owning collection. The feature then makes it one less step,
*if* the one attribute they care about having pre-loaded is that
one. Otherwise, even their experience is not enhanced at all by the
new feature.
How could I possibly justify such a design decision ?
--
Jon Siddle, CoreFiling
session (no SQL is sent to the DB for c.parent)
These apprent do-nothing loops are starting to clutter the code. There
must be a better way.
Thanks
Jon
--
Jon Siddle, CoreFiling Limited
Software Tools Developer
http://www.corefiling.com
Phone: +44-1865-203192
--
You received this message
On 13/09/10 16:45, Michael Bayer wrote:
On Sep 13, 2010, at 8:48 AM, Jon Siddle wrote:
I'm sure I'm missing something simple here, and any pointers in the right
direction would be greatly appreciated.
Take for instance the following code:
session = Session()
parents = session.query(Parent
