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
As the "safe-mode" storage uses bincode to serialize the data into a file on disk, there should be some tests that this won't break.
rkv needs to be able to load data written with previous versions. bincode doesn't necessarily guarantee that (though to my knowledge they haven't broken it either).
Some tests could be useful.
Write some data into a file, then use that file's data in a test (either load it or embed it directly) and check that it can be loaded and contains the expected data. Dependency updates shouldn't break that test then.
The text was updated successfully, but these errors were encountered:
Hmm, I think I misread your original comment. You meant storing the current version of a database file, and persisting that as a test for future versions. Gotcha – yes, this is a good idea!
As the "safe-mode" storage uses bincode to serialize the data into a file on disk, there should be some tests that this won't break.
rkv needs to be able to load data written with previous versions. bincode doesn't necessarily guarantee that (though to my knowledge they haven't broken it either).
Some tests could be useful.
Write some data into a file, then use that file's data in a test (either load it or embed it directly) and check that it can be loaded and contains the expected data. Dependency updates shouldn't break that test then.
The text was updated successfully, but these errors were encountered: