-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kees Nuyt wrote: > I assume the OP wants to collect updates from more than one > webpage into one logical transaction, where every webpage > contains another part of the data to be changed. In that > case a memory database wouldn't work because it would > disappear between page requests.
More accurately the memory database has the same lifetime of the database connection in that process, and depending on how PHP is hosted there could be multiple different processes involved in requests, and processes could exit after processing a number of requests. (It is important to clarify that SQLite doesn't spuriously disappear in memory databases :-) > That would work. I would use the main database all the way > though, The OP is trying to prematurely optimize access away from a potentially busy/locked main database :-) > One common design pattern It may be worth starting a section of the wiki with various design patterns for common tasks. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkkepTEACgkQmOOfHg372QRPDgCg2SmHXsmdyR93ffvR0SWSWMEp zFoAniPt4WzVXIjm/Iq/qrru5FEVHhw2 =r/yF -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
