My application is running 24x7 with huge data loads and around 10 open connections all the time.
On Dec 19, 2007 4:50 AM, Renaud HUILLET <[EMAIL PROTECTED]> wrote: > > I have that for my soft and it works fine. > > I also have a swap mecanism to update the sqlite file : the daemon gets the > sqlite file's name from a filemapped into memory. > When a new file has been generated, another batch updates the filemap with > the new sqlite file's name. > The daemon sees the file name has changed (with no I/O since it is mapped > into memory) , kills the SQLIte connection and opens a new one. > > Best Regards. > Renaud> Date: Tue, 18 Dec 2007 14:27:28 -0800> From: [EMAIL PROTECTED]> To: > [email protected]> Subject: [sqlite] sqlite in a daemon> > Hello,> > I > am considering writing a daemon that would keep the sqlite connection opened > forever (at least in the "daemon" sense of forever). Is it a good idea? Any > experience you could share about that kind of design?> Thanks> > > > > > ____________________________________________________________________________________> > Looking for last minute shopping deals? > Find them fast with Yahoo! Search. > http://tools.search.yahoo.com/newsearch/category.php?category=shopping > _________________________________________________________________ > Express yourself instantly with MSN Messenger! Download today it's FREE! > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
