On 02/27/2016 08:48 AM, Will Angenent wrote:
The code was just to reproduce the exact SQLA error by doing what alembic and
SQLA are doing and additionally determining when the garbage collector runs.
The theory is that garbage gets collected somewhere in between
list(_mapper_registry) in
On 02/27/2016 07:26 AM, Piotr Dobrogost wrote:
On Friday, February 26, 2016 at 7:45:46 PM UTC+1, Jonathan Vanasco wrote:
I'm not either, and I'm scared of the SQL that would be generated
and the wire traffic/memory if there were. That would be subselects
within subqueryloads
The code was just to reproduce the exact SQLA error by doing what alembic and
SQLA are doing and additionally determining when the garbage collector runs.
The theory is that garbage gets collected somewhere in between
list(_mapper_registry) in configure_mappers and what happens in
On Friday, February 26, 2016 at 7:45:46 PM UTC+1, Jonathan Vanasco wrote:
I'm not either, and I'm scared of the SQL that would be generated and the
> wire traffic/memory if there were. That would be subselects within
> subqueryloads within... this also seems a bit more about "updates to
>
