4 ms·
> Features that regularly add data to the DB (e.g. visited URIs), but have no expiration policy for the data, can easily cause the DB to balloon into tens or hu
by adrianmonk 6y ago
> Features that regularly add data to the DB (e.g. visited URIs), but have no expiration policy for the data, can easily cause the DB to balloon into tens or hundreds of MBs.
I don't know if it's fair to call that a SQLite pitfall. If they can recommend an alternative storage option where this problem doesn't occur, I'd be extremely interested to hear about it.
- hobs 6y agoI think the only real critique is that a file system already has systems to identify individual ballooning items, whereas the database would be a single container that is opaque to many basic users.