Q) Record order from find() and support for sorting? about nedb HOT 1 CLOSED

Hello,

There is no support for sorting results yet but I think it is needed, along with support for limit and skip and I'll implement it in the near future. Nothing can be said about the order of results if no index is used on the field on which you expect a sort (in your case the timestamp). As you guessed, that's because of the binary tree indexing that will keep an order on _id if you don't specify an index on the timestamp. The order on _id is of course completely arbitrary as the _ids are random.

That's why it would help to add an index on the sort field but that will not be very reliable if you have multiple indexed fields. So for now your best choice is to use javascript's sort() which is very fast on arrays of less than ~10k docs, and wait for a more robust implementation of sort, skip and limit

from nedb.