2 ms·
You're right and when I thought about it more I considered that "supervisor" isn't what I would want. Rather I'm thinking raising errors to the program that emb
by jemmyw 1y ago
You're right and when I thought about it more I considered that "supervisor" isn't what I would want. Rather I'm thinking raising errors to the program that embeds sqlite so that it can decide what to do. I do have a desktop app that uses sqlite and I'd rather it raised an error than tried to recover.
- ulfgard 1y agoBut getting back into a well-defined state which you can communicate via an error is a viable recovery strategy. This state can be "the database is corrupt", allowing for a restore from backup, it can also be "shut down gracefully" and communicate that. Especially for databases there is a ton to concinder: what about database entries that are not committed yet? When you run into oom, should you at least try to commit the data still in ram by freeing as much space as possible?