Quote:
Originally Posted by CarlosinFL
I've only noticed this in PostgreSQL.
|
Actually all DBMS behave like that.
As r937 has pointed out, the lack of an ORDER BY is the reason.
The
only way to guarantee a specific order of your row is to use an ORDER BY
Actually you don't necessarily need to change the data to see this behaviour
PostgreSQL (or other DBMS). PostgreSQL can e.g. use the result of another's session table scan for your statement (to optimize I/O).
Unless you explicitely request a sort order the DBMS is free to return the rows in any order it seems suitable (to speed up the processing)
Btw: your terminology is a bit confusing. You did not "edit" the rows using "ALTER" but "UPDATE"