3 ms·
Why would you want to use PostgreSQL in the contexts that SQLite is used? SQLite is fantastic when you need a data store for mobile or embedded use, you'd like
by bitserf 13y ago
Why would you want to use PostgreSQL in the contexts that SQLite is used?
SQLite is fantastic when you need a data store for mobile or embedded use, you'd like ad-hoc queries over your data with the option of adding indexes to speed up frequently used ones, you want transactional update to the data, and multi-user access is not a problem.
It's basically a much better replacement for the hash table on a disk approach of DBM libraries.
PostgreSQL would just be total overkill for this kind of scenario.
- nraynaud 13y agoI just would like the simplicity of use of sqlite on my server. No socket, no connection, no driver that has to match the server, no config file in /etc, no user in /etc/passwd, no cruft.
- jeffasinger 13y agoThe separation between the client and server that brings all the 'cruft' makes it a lot simpler to have high performance concurrent operations, a major advantage of a full DBMS over SQLite
- dragonwriter 13y ago> I just would like the simplicity of use of sqlite on my server. The simplicity comes from largely from not supporting multiple user accounts (authn/authz are left to the owning application), and secondarily (I think) from not being designed to support large numbers of connected processes. If your server need fits that profile, then you can use SQLite and benefit from its simplicity. But if -- as is often the case -- it doesn't, you can't, and its not because no one has merged SQLite with PostgreSQL, its because there is inherent complexity that comes with serving certain use cases.