HACK13 on Nostr: npub1anemw…z7zqz I love #SQLite. I worry about it scaling up to meet my needs. ...
npub1anemw74fksv62v9ncq0kvjf8gayqhf0kekl498gmhn67eg4srfhq2z7zqz (npub1ane…7zqz) I love #SQLite. I worry about it scaling up to meet my needs. Right now, it is fine because the number of instances will never be that big. However, what about going forward though? I plan on adding a user directory, which will need tons of extra rows to query.
SQLite is fast for simple queries, but when users start making several queries across multiple rows, other database platforms can handle those queries better. Also, the database isn't bound to a single file but multiple to prevent locking during queries. I am willing to try to keep using SQLite because it saves me overhead... but I am just not sure of the longevity it could support with me building extra stuff on top.
SQLite is fast for simple queries, but when users start making several queries across multiple rows, other database platforms can handle those queries better. Also, the database isn't bound to a single file but multiple to prevent locking during queries. I am willing to try to keep using SQLite because it saves me overhead... but I am just not sure of the longevity it could support with me building extra stuff on top.