I'm interested in how sqlite works differently to the SQL systems which keep a daemon running as a background task. One of the advantages of having a daemon which persists between runs of an application is that the daemon can keep its own list of ORDERs, and JOINs which are asked for frequently, and decide to maintain them even when no SQL-using application is running. This can give the impression that something is being done very quickly, when in fact the majority of the time was taken during a previous run of the application. It can be particularly hard to figure out what a performance test means under these circumstances.
But the problem is that I like the way sqlite works. I like the tiny library, I like the way that the SQL library is entirely inside my application, and any CPU load is mine. I like knowing that when my app quits, nothing is going on. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
