SQLite should be used when you are writing applications in which you do not want the user to even know they are using a database. It is embedded only and isn't designed with security or concurrency to support a mutli-user load like PostgreSQL/MySQL/Oracle/Microsoft SQL Server. Something like Postgres should be used when you want to allow multiple users to access data at the same time.
You can have multiple processes use SQLite but you must manage the access yourself. There is the concept of transactions so you do have isolation levels. I usually have created a database thread and allow db access in that thread only. However, my uses of SQLite have always been as a replacement to a custom data file format for a single application. Storing everything in a single file makes backup easy as well as transporting the data from one machine to another. The single file is trivial to move around and get in the right place. Something like Postgres is more difficult to move the data files. SQLite is designed to access very large files (much bigger than 13MB). Typically, SQLite's perf number will be better than Postgres, et. al. because it is lighter weight. You can use it for a server process but you are really in charge. Think about using SQLite like you would a custom file format and you will understand most of the situations it works well. If you have a picture that has a classic RDBMS in it, SQLite is probably not the right package. Andrew On Thu, 12 Feb 2004, [EMAIL PROTECTED] wrote: > Just looking for some feedback about how people are using sql lite > Is it mostly embedded systems? > Why and in what situations would i use sqlite over postgres ? > Why and in what situations would i use postgres over sqlite ? > I also have a few questions about scalability ? > > Can multiple processes use the same database file concurrently ? > What are the locking granularities for simultaneous thread access ? > What are the costs benefits of storing everything in one file ? > I saw the benchmarks, but was concerned that the database size was only > 14meg. > > Just trying to make an informed decision. > I have needs for both a single user embedded database and a scalable > multiuser database. > I'm trying to find out how far sqlite will stretch from single use > embedded toward multiuser scalable. > > Thanks, > Kevin > > P.S. I would be happy to format replies and place them on your wiki for > future reference. > > Also do you have a mailing list archives somewhere I could search through ? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
