This PR is purposed to fix the issue #79 by replacing the previous internal implementaion of database methods that directly stored and retrieved serialized vector collections to Sled with writing and reading them from a file.
After talking to the maintainers of Sled, it makes sense that Sled is not built to store Collection due to its size reaching 100MB to 10GB per collection. Instead now, OasysDB database serialize and store collections directly into files.
The file reference to where the collection is stored is now packaged in CollectionRecord along with other utility details like collection length and time the database is created and updated.
Testing
[x] I have tested this PR locally.
[x] I added tests to cover my changes, if not applicable, I have added a reason why.
This PR doesn't change how the API works to change the test. But this PR is not compatible with the previous release.
Chore checklist
[x] I have updated the documentation accordingly.
[x] I have added comments to most of my code, particularly in hard-to-understand areas.
Purpose & approach
This PR is purposed to fix the issue #79 by replacing the previous internal implementaion of database methods that directly stored and retrieved serialized vector collections to Sled with writing and reading them from a file.
After talking to the maintainers of Sled, it makes sense that Sled is not built to store
Collectiondue to its size reaching 100MB to 10GB per collection. Instead now, OasysDB database serialize and store collections directly into files.The file reference to where the collection is stored is now packaged in
CollectionRecordalong with other utility details like collection length and time the database is created and updated.Testing
This PR doesn't change how the API works to change the test. But this PR is not compatible with the previous release.
Chore checklist