[mailto:sqlalchemy@googlegroups.com] On
Behalf Of Michael Bayer
Sent: 13 July 2013 22:46
To: sqlalchemy@googlegroups.com
Subject: Re: [sqlalchemy] The cost of defer()
anyway, with some profiling of loading 1000 rows with six deferred cols, the
function count with the defer was over 50K
Of Michael Bayer
Sent: 11 July 2013 15:34
To: sqlalchemy@googlegroups.com
Subject: Re: [sqlalchemy] The cost of defer()
the path would be to figure out if the logic of a per-query defer option
can somehow be linked to the attribute when it hits its normal refresh
logic - if those attribute
the path would be to figure out if the logic of a per-query defer option can
somehow be linked to the attribute when it hits its normal refresh logic - if
those attribute were set up as deferred at the mapper config level (where
deferred is usually used), you wouldn't see this overhead since
is cheaper than not loading it.
From: sqlalchemy@googlegroups.com [mailto:sqlalchemy@googlegroups.com] On
Behalf Of Michael Bayer
Sent: 11 July 2013 15:34
To: sqlalchemy@googlegroups.com
Subject: Re: [sqlalchemy] The cost of defer()
the path would be to figure out if the logic of a per-query defer option
is cheaper than not
loading it.
From: sqlalchemy@googlegroups.com [mailto:sqlalchemy@googlegroups.com] On
Behalf Of Michael Bayer
Sent: 11 July 2013 15:34
To: sqlalchemy@googlegroups.com
Subject: Re: [sqlalchemy] The cost of defer()
the path would be to figure out if the logic of a per
it.
From: sqlalchemy@googlegroups.com [mailto:sqlalchemy@googlegroups.com] On
Behalf Of Michael Bayer
Sent: 11 July 2013 15:34
To: sqlalchemy@googlegroups.com
Subject: Re: [sqlalchemy] The cost of defer()
the path would be to figure out if the logic of a per-query defer option can
