Known issue with index sizes in sqlightning

LumoSQL / archive1-LumoSQL-on-github

Initial work on SQLite and LMDB integration

https://lumosql.github.io/LumoSQL/

Other

68 stars 14 forks source link

Known issue with index sizes in sqlightning #5

Closed maxwell-k closed 4 years ago

maxwell-k commented 4 years ago

See https://github.com/LMDB/sqlightning/issues/1

danshearer commented 4 years ago

This part of the ongoing discussion about where to intercept SQLite APIs. We should be at a high enough level so that the fix for this (probably chained keys as hyc said in the bug report referenced above) applies to all storage backends. That suggests higher up the stack than where libkv would go.

danshearer commented 4 years ago

The backend abstraction layer design so far provides large key support for the backends that need it (eg LMDB does but RocksDB does not.)

danshearer commented 4 years ago

Not a bug. Moved to https://lumosql.org/src/lumosql/wiki?name=lumosql-storage-api . It isn't a bug because we are implementing generic key handling in the storage API, and that also involves some sensitivity into the different ways MVCC is implemented by various K-V stores.