In 3.1.6 Index you find this:

# The records in an index are always sorted according to the records key.
# However unlike object stores, a given index can contain multiple records
# with the same key. Such records are additionally sorted according to the
# records value.


And in a note in the "steps for iterating a cursor" you find:

# records is always sorted in ascending key order. In the case of 
# source being an index, records is secondarily sorted in ascending
# value order.

That is all fine and dandy, because for an index, the key is "toyota" and the value is in fact a *pointer to the referenced record*, so value will be the *key* of the objectstore record.


Technically there is no problem, however, those sentences up there might easily confuse humans (I always have to read it twice). So I hope we can tweak the wording; In "3.1.6 Index"

# The records in an index are always sorted according to the records key.
# However unlike object stores, a given index can contain multiple records
# with the same key. Such records are additionally sorted according to the
# records value (meaning the key of a record in a referenced object store)

And in the steps for iterating a cursor:

# records is always sorted in ascending key order. In the case of 
# source being an index, records is secondarily sorted in ascending
# value order (value in an index is a key from the referenced object
# store).


Please feel free to make it even better or clearer, I'm not super happy about the fixes.

Yeah, and sorry for making bugs at this time, but I hope we want to fix stuff even after CR. ;-)