This content has been marked as final. Show 8 replies
Thanks for your response
I am just doing a small test on insertRowAtRangeIndex(4,newRow);
and it adds the newRow at the 4th poistion (0-based index).
I also need to refersh table once I hit exceute Commit
and bring back newely created row to readyonly mode
so, I am doing voname.executeQuery();
and it puts the row at the bottom, as I expected, because it still read the data from database.
Can you focuse more light on this?
Once again thank you for your response,
As I said before, you can't put a row in the db at position x.
You need an attribute the db can use to order the rows upon. This is no easy task because you have to shift all rows (change an attribute) after the newly inserted one, or think about an algorithm which calculates the attribute for the new row (given the order attribute from the current row and the next row).
I agree 100% to Timo. If you do not have a "order by" clause in your select statement you can't predict the row order. It depends e. g. on the physical storage place of the record in the DB block and the access path of the optimizer.
If you need further assistance it would be helpfull to explain the use case more detailed (e.g. what's the idea behind it, why you do not have a sort criteria in the DB, ...)