Update Multiple Scroll Sequence Behavior [message #4294] |
Thu, 26 June 2014 08:50 |
kong
Messages: 90 Registered: December 2011
|
Member |
|
|
Selecting several records in List1 and then clicking Update button will bring up detail screens for the selected records one by one for editing. And by clicking the Submit Next button, the current record will be saved and the next record will be presented, etc.
However, I noticed that sometimes, after updating a record and clicking Submit Next, the sequence of the selected records as associated to the scroll bar could have changed. This could result in some strange behavior like getting presented with already processed records after clicking Submit Next, while unprocessed records could have moved up in the sequence and hence will not be presented in subsequent Submit Next's. There is no way to tell where unprocessed records might be hiding in the sequence, other then by going through all the records again one by one.
I suspect this has to do with the way each selected record for update is read from the DB using a SELECT statement with OFFSET xx, where xx is the sequence in which records are linked to the scroll bar. This could result in 1) when a sort order is not defined in the SELECT statement, there is no guarantee that the order of returned records for the same set of records SELECT will be in the same order every time (I noticed this especially in PostgreSQL) and 2) when a sort order is defined and an edit/update of a record changed the value of a field that was part of the ORDER BY clause then this could dynamically change the sequence as well.
|
|
|
|
|
|