3 ms·
You must not be doing very many writes, because all writes lock the particular table from all other writers. Better databases have row level locking which allo
by Thetawaves 10y ago
You must not be doing very many writes, because all writes lock the particular table from all other writers.
Better databases have row level locking which allows many users to update the same table at the same time.
- And this isn't all that strange, say you wanted to store a timestamp for the last time a user visited your site, session ids, etc.
- juskrey 10y agoGood point. Still with thousands of users per day I can hardly experience any difficulties. I guess with a sane app architecture and coding this is not a problem up to a million/day.. for, say, some generic CMS site. UPD: Good explanation http://sqlite.org/whentouse.html http://sqlite.org/whentouse.html
- Arcsech 10y ago> Better databases have row level locking which allows many users to update the same table at the same time. Nitpick: Databases that make different tradeoffs have row level locking. SQlite is very good, for the niche that it's in, which is a lightweight, embeddable database for primarily single-user applications. It's incredibly popular in that space, to the point of likely being the most-used database on the planet by number of running instances since it's in so many smartphones/embedded devices.
- Thetawaves 10y agoNone of the use cases you mention are 'multiuser' so I'm going to take this as just a helpful hint to the internet at large.