By default, LevelDB orders keys in the key-value store as byte arrays sorted lexicographically. 

LevelDB allows the user to implement their own custom ordering on the keys; iteration over the database will then be performed in this order. We of course use this in android history...and IndexedDB. IndexedDB uses binary strings with arrays and paths and other such features and we have a 1,900 line file that implements comparisons here.

So what do we do here? Do we hard code this into the leveldb interface?