L
Lieven De Foor
Guest
Hi George, Let me quickly try to explain how I encountered this problem, to give an insight. We have a grid that can show the data of a temp-table. The data comes from a db table with the same structure (fields and indexes) as the temp-table. The user is allowed to press the END key, after which we retrieve the LAST batch of n records from the db and populate the temp-table with (only) those records. When the user scrolls UP, the moment the first record gets becomes visible, the server is requested for the next batch of records (which is logically the previous batch, as the user is scrolling up). When a non-unique index is used, this scenario causes problems. In that case, because the ROWIDs of the records matters for the sorting of duplicate index values, the next batch retrieved from the server will get sorted AFTER the records already on the client, instead of BEFORE, since their ROWIDs are higher (newly created records on the client), whereas they were lower/before on the server...
Continue reading...
Continue reading...