How does a!QueryEntity works? I am fetching data from a table through a!que

How does a!QueryEntity works?
I am fetching data from a table through a!queryEntity. Table has n number of columns from which only one can have unique data (Primary Key Column). Others can have duplicate data.
I tried to fetch data in batchSize of 5. The problem is, for a column "Name", if a name is same in 12 rows, and I try to fetch data sorted by "Name" for startIndex 1. The identifiers (primary key) comes: 14; 18; 17; 16; 15. Then I change the startIndex to 6, the identifier comes: 19; 18; 17; 16; 15. Now I change the startIndex to 11, the identifier comes: 16; 15; 4; 7; 6.
If you observe, there is some same data coming in every Set (18,17,16,15 -- > 18,17,16,15 --> 16,15). After that identifier changes because same name is there in table for 12 times only.

Can anyone explain why is this happening ?
Why the same/duplicate data is coming even when data is sorted on that column and startIndex is changing?
I am using a Oracle DB. I ha...

Query

OriginalPostID-184999

OriginalPostID-184999

  Discussion posts and replies are publicly visible

Parents
  • 1. Aggregation is required when I need Unique results for that column, that is not requirement here. Only "Name" column has same entries. All other columns has different entries. So I need all the data.

    2. I understand what is StartIndex and Batchsize and that's why I have raised this question that while changing for startIndex...it is giving me the same results....which shows, as per my understanding, that in DB Row 2-5 contains all the same data which is in Row 7-10 (even PK because startIndex has been changed) in my example...which is actually not the case. The data is different.
Reply
  • 1. Aggregation is required when I need Unique results for that column, that is not requirement here. Only "Name" column has same entries. All other columns has different entries. So I need all the data.

    2. I understand what is StartIndex and Batchsize and that's why I have raised this question that while changing for startIndex...it is giving me the same results....which shows, as per my understanding, that in DB Row 2-5 contains all the same data which is in Row 7-10 (even PK because startIndex has been changed) in my example...which is actually not the case. The data is different.
Children
No Data