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
чт, 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
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
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
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
> 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