New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Roadmap, acidity and transactions: consider this #14

Open

o0101 opened this issue Nov 14, 2020 · 3 comments

Collaborator

o0101 commented Nov 14, 2020

https://danluu.com/deconstruct-files/

Collaborator Author

o0101 commented Nov 17, 2020

Moving towards ACID is interesting.

Some ideas

use fdatasync and crash if it errors
provide an option to check the consistency of the database (check all records against their table's schemas)
add an error check to each record, being a hash of the record string, with our without the hash slot present, with an option to add a check to every field of the record, by adding a hash for every field of the record, as well

Collaborator Author

o0101 commented Nov 27, 2020

Also consider copy on write mode

https://nodejs.org/api/fs.html#fs_file_copy_constants

https://levelup.gitconnected.com/how-to-create-a-copy-on-write-clone-of-a-file-in-node-js-443cfa2b18d9

Collaborator Author

o0101 commented Nov 28, 2020

And ...

https://www3.physnet.uni-hamburg.de/physnet/Tru64-Unix/HTML/APS33DTE/DOCU_009.HTM#:~:text=Synchronized%20I%2FO%20is%20useful,of%20data%20on%20that%20device.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment