On Sat, 15 Nov 2008 02:32:21 -0800, Roger Binns <[EMAIL PROTECTED]> wrote in General Discussion of SQLite Database <sqlite-users@sqlite.org>:
>-----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 :-) Very true. To clarify some more: In general a database connection (and thus an SQLite memory database) is lost as soon as PHP has processed the request and sent a response page. >> 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 :-) I secretly hope a complicated design pattern scared him away from doing that ;) >> One common design pattern > >It may be worth starting a section of the wiki with >various design patterns for common tasks. Yes, but I don't think the SQLite wiki is the appropriate place, as this is a generic session and transaction management (OLTP) issue, which has more to do with application frameworks than with a specific database engine. The SQLite wiki could contain links to relevant fora, but I wouldn't know one from the top of my head. Searching newsgroup comp.lang.php would be a good start. >Roger -- ( Kees Nuyt ) c[_] _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
