Sometimes you want to write a script that is chatty with the database, perhaps it imports a bunch of stuff with conditional logic from a collection of files, or other kinds of data pipeline workloads. When you're doing this, it's rarely helpful for the database to commit every change to storage. In this mode, Fireproof would have a manual save operation, and only output one car file for each save.
This is perfect for code notebooks because you can pick up the processing from the save point, and track old savepoints to correspond with old versions of the notebook code, etc.
Sometimes you want to write a script that is chatty with the database, perhaps it imports a bunch of stuff with conditional logic from a collection of files, or other kinds of data pipeline workloads. When you're doing this, it's rarely helpful for the database to commit every change to storage. In this mode, Fireproof would have a manual save operation, and only output one car file for each save.
This is perfect for code notebooks because you can pick up the processing from the save point, and track old savepoints to correspond with old versions of the notebook code, etc.