-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
feat: cleanup old entries in the sqlite #21
Comments
or maybe remove the entries on the fly, while new are being inserted (though this will slow down the insertion process...) |
..or maybe simply keep only one state per contract....which may result in a slight risk of that newer state will be overwritten by the older one (if the evaluation of the the 'older' interaction will happen to end after evaluation for the 'newer' interaction - in a scenario, where contract has a lot of interactions registered in a short period of time) |
UNIQUE on contractID, trigger function that neglects INSERT if sortKey is smaller that the inserted |
Trigger for ensuring only the newest state is stored #21
run periodically (once a day?):
on the node.sqlite db.
Watch out for the WAL file size after cleanup - rm might be needed.
The text was updated successfully, but these errors were encountered: