Re: [sqlalchemy] Disable `session_identity_map` for `_instance_processor`

2017-11-23 Thread Simon King
On Thu, Nov 23, 2017 at 6:55 PM, Антонио Антуан wrote: > > > чт, 23 нояб. 2017 г. в 20:27, Mike Bayer : >> >> On Thu, Nov 23, 2017 at 8:44 AM, Антонио Антуан >> wrote: >> > >> >> A Query can have lots of entities in it, and if

Re: [sqlalchemy] Disable `session_identity_map` for `_instance_processor`

2017-11-23 Thread Антонио Антуан
чт, 23 нояб. 2017 г. в 20:27, Mike Bayer : > On Thu, Nov 23, 2017 at 8:44 AM, Антонио Антуан > wrote: > > > >> A Query can have lots of entities in it, and if you're doing sharding a > >> single result set can refer to any number of shard identifiers

Re: [sqlalchemy] Disable `session_identity_map` for `_instance_processor`

2017-11-23 Thread Simon King
On Thu, Nov 23, 2017 at 5:27 PM, Mike Bayer wrote: > On Thu, Nov 23, 2017 at 8:44 AM, Антонио Антуан wrote: >> >>> A Query can have lots of entities in it, and if you're doing sharding a >>> single result set can refer to any number of shard

Re: [sqlalchemy] Disable `session_identity_map` for `_instance_processor`

2017-11-23 Thread Mike Bayer
On Thu, Nov 23, 2017 at 8:44 AM, Антонио Антуан wrote: > >> A Query can have lots of entities in it, and if you're doing sharding a >> single result set can refer to any number of shard identifiers within >> not just a single result set but within a single row; they might have

Re: [sqlalchemy] Disable `session_identity_map` for `_instance_processor`

2017-11-23 Thread Антонио Антуан
See, that `Query.get` using `get_from_identity` instead of `instances` with key, constructed into `_get_impl`. Could you point to another places where same problem (described into my first message) can be appeared? чт, 23 нояб. 2017 г. в 16:44, Антонио Антуан : > > > A Query

Re: [sqlalchemy] Disable `session_identity_map` for `_instance_processor`

2017-11-23 Thread Антонио Антуан
> A Query can have lots of entities in it, and if you're doing sharding a > single result set can refer to any number of shard identifiers within > not just a single result set but within a single row; they might have > come from dozens of different databases at once In my case it is not