Guys, The problem is that order of fields serialization is unknown for regular objects, where "regular" stands for non-Binarilyzable class. Reflection returns fields in unpredictable order. For this reason you cannot match fields order between class and QueryEntity. This is why we introduced sorting, and this is why idea to rely on QueryEntity doesn't work.
On Mon, Apr 10, 2017 at 7:01 PM, Sergi Vladykin <[email protected]> wrote: > Why "regular" are different here? > > Sergi > > 2017-04-10 18:59 GMT+03:00 Pavel Tupitsyn <[email protected]>: > > > QueryEntity sorting is not an option for "regular" classes with > reflective > > serialization. > > We have to use alphabetical. > > Also, same class can participate in multiple query entities. > > > > 10 апр. 2017 г. 18:52 пользователь "Dmitriy Setrakyan" < > > [email protected]> написал: > > > > On Mon, Apr 10, 2017 at 8:28 AM, Sergi Vladykin < > [email protected]> > > wrote: > > > > > The decision to use alphabetic order looks strange here. Using order > > > provided in QueryEntity and require from user to have the same order > > > in Binarylizable > > > looks more reasonable. > > > > > > > I think this would be much harder to verify. Alphabetical order is more > > intuitive, no? > > >
