Timur Kristóf
Timur Kristóf
@nwbrad Well if you think that something like that 53-bit integer would help, I could implement that for you.
@nwbrad However it won't be a drop-in replacement because then the new database will be binary incompatible with the old one.
@nwbrad It is possible, but then you will have 32-bit and 64-bit keys mixed in the same database, so you will need to disable the `MDB_INTEGERKEY` optimization. Then it can...
@nwbrad I said the new **database** (with 64-bit keys) would not be binary compatible with the old one (with 32-bit keys). I wasn't talking about the module itself.
@nwbrad Are you still interested in this? I've looked at the V8 docs, but it seems it doesn't have a suitable data type for storing these keys: https://v8docs.nodesource.com/node-8.9/dc/d0a/classv8_1_1_value.html
The V8 `Integer::New` only takes a 32-bit number, unfortunately (even though it returns its value in 64-bit).
@nwbrad Unfortunately. Some digging also turned up this: https://github.com/thlorenz/v8-perf/issues/3#issuecomment-45545604 Relevant quote: > V8 integer sizes: > > * In 64-bit up to 32-bit signed > * In 32-bit up to...
@nwbrad Allright, I guess I can do it like this!
@matthewaveryusa Sounds good, though then the feature needs to be `#ifdef`ed in such a way that it only works on node versions that support bigint. Looking forward to the PR.
@nwbrad Thanks for reporting this. Can you please run `node-lmdb` inside `gdb` to see a better backtrace? Also, do you use the latest version? If you are unfamiliar with gdb,...