On 12/21/25 12:21, Shaun Campbell wrote: ... Just checking my code though and it appears I
never sorted the sql select statement anyway, so I could never guarantee the order of insertion and hence result display, although I don't know why the database server would change its ordering. I'll check with the dba.
Because updates are typically done as creating a new row and deleting the old one, for that ACID thing. So if the database is getting updates, its row order will diverge from the original insertion order over time. And then it may be shrunk/vacuum'ed/optimized, which may or may not re-arrange the records on disk again into something different and equally non-obvious.
I tend to think of Solr the same way: the order is anything unless explicitly specified.
Dima
