Persisted robjects currently have random uuids and half of that is the random
local db id of the object.
These are great for global uniqueness of objects but are hard to work with when
directly querying/exploring/repairing the db with sql.
So need a seq incrementing integer, only unique in the local db, or perhaps a
first-persisted-time UTC timestamp. otm
The latter has some intriguing possibilities for approximate distributed cache
consistency algorithms etc.
Original issue reported on code.google.com by relis...@gmail.com on 6 Nov 2013 at 11:26
Original issue reported on code.google.com by
relis...@gmail.com
on 6 Nov 2013 at 11:26