Timur Kristóf
Timur Kristóf
> It would allow to store strings as keys in lexicographical order. Imagine that you are implementing full-text search and store keywords as keys in a table. Then, if keys...
@degifted @da77a Here is my opinion about this pull request: Unfortunately, it breaks compatibility with existing users of node-lmdb, so I can't accept it as-is. And then, there is a...
@da77a That sounds very reasonable. You convinced me! @degifted Would it be okay for you to modify the patch so that the change would be triggered by a different, new...
@degifted @da77a Thank you guys for the great discussion. The idea to add another flag to `dbi.open` didn't occour to me, but sounds good and sounds like the correct™ way...
@nwbrad You can use a `Buffer` as key, which can be as big as you wish.
@nwbrad I will think about what the best way is to implement this. Maybe there could be a special buffer key type which only allows 64-bit buffers, and I could...
@nwbrad I would not use a UInt64, because that would prevent users that use actual 64-bit numbers in other LMDB applications from using their existing databases with node-lmdb. About the...
The values cannot be managed via a normal JS number variable because of what you said - it doesn't support 64-bit values properly.
@nwbrad Why do you not want to work with buffers?
@nwbrad Why is it untested? Why would you need to change all existing javascript code?