Context Navigation

Changes between Version 1 and Version 2 of Ticket #35977, comment 3

v1	v2
3	3	The lack of ordering consistency when retrieving objects from the database without an explicit ordering is not a Postgres or serialization specific problem.
4	4
5		When ~~no `ORDERY BY` is~~ specified the database can choose to return values in the order it wants which is usually the fastest one. In the case of database like MySQL that usually means by primary key as that's how the data is clustered/organized on disk while on Postgres it depends on multiple factors.
	5	When `ORDERY BY` is not specified the database can choose to return values in the order it wants which is usually the fastest one. In the case of database like MySQL that usually means by primary key as that's how the data is clustered/organized on disk while on Postgres it depends on multiple factors.
6	6
7	7	The patch you are proposing would be backward incompatible for two reasons