Even afterrestarting the application, the updated record keeps showing at the end of the grid.
Has anyone an idea about what couldbe the cause of such a behavior.
basically i treat them as in "random" order (which is nottrue, but helps me remember to never count on the "default" ordering. To hope that the database would do that automatically for you is IMHO wrong.
One way I can think of is to store the ordering information along with the user and then fetch the items in the desired order while displaying.
Make sure you have some primary key in this table to uniquely identify these row.depesz -- quicksil1er: "postgres is excellent, but like any DB it requires a highly paid DBA. " :) - blog dla ciebie (i moje CV) You are right about the fact that the rows don't keep the order they where created with at the start. I will explain more my case : I am writing an application where here is some resources to planevents on.I want to provide the user with the ability to customize the order in which resources are displayed on thescreen.I hope that you understand my issue and I will provideany explanations if someting isn't clear enough.Thanks to all Nacef why do you think it stays in the same place in db? How it works in general terms (simplified, but I lack the expertise to give a complete explanation even if one was required) is: When you update a row the old row is marked as dead and a new row is inserted.