I assume it's because of iterators in read-time, which go over results do
merging/reducing/collating results one-by-one that is not so well suited for
jumping to arbitrary offsets, given the practically huge number of columns
involved, right?
No really, you can have a slice that starts in
There are several reasons. First there is no absolute offset. The
rows are sorted by the data. If someone inserts new data between your
query and this query the rows have changed.
Unless you doing select queries inside a transaction with repeatable
read and your database supports this the query
Thanks Ed, for the clarifications
Yes you are correct that the apps have to handle repeatable reads and not
the databases themselves when using absolute offsets, but SQL databases do
provide such an option at app's peril!!!
Slices have a fixed size, this ensures that the the query does not
