You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LMDB stores key-value pairs for named databases in the default database, which makes it dangerous for an application to open both named databases and the default database within the same environment using rkv, as the default database will contain pairs they didn't add, and those pairs cannot be read by rkv (because they aren't formatted the way rkv expects, i.e. by using bincode to serialize Rust values to bytes).
Thus we should prevent applications from opening both named databases and the default database within the same environment via a compile time (ideally) or runtime error.
The text was updated successfully, but these errors were encountered:
In #101 I removed the ability to create a default database. This removes that problem. It makes creation a bit more verbose, but it's safer and more general, IMO.
LMDB stores key-value pairs for named databases in the default database, which makes it dangerous for an application to open both named databases and the default database within the same environment using rkv, as the default database will contain pairs they didn't add, and those pairs cannot be read by rkv (because they aren't formatted the way rkv expects, i.e. by using bincode to serialize Rust values to bytes).
Thus we should prevent applications from opening both named databases and the default database within the same environment via a compile time (ideally) or runtime error.
The text was updated successfully, but these errors were encountered: