Re: [sqlite] Berkeley DB vs. SQLite for threaded application

On 2008 January 16 (Wed) 04:57:42am PST, [EMAIL PROTECTED] wrote: > Tomas Lee <[EMAIL PROTECTED]> wrote: > > I've got an application that has Berkeley DB embedded in it. I want > > to replace Berkeley DB with SQLite. (I plan to use the 3.5.4 > > almagamation, which is the latest I could find.) T

Re: [sqlite] Berkeley DB vs. SQLite for threaded application

Tomas Lee <[EMAIL PROTECTED]> wrote: > I've got an application that has Berkeley DB embedded in it. I want > to replace Berkeley DB with SQLite. (I plan to use the 3.5.4 > almagamation, which is the latest I could find.) The thing is, this > application uses threads. I know threads are evil, bu

Re: [sqlite] Berkeley DB vs. SQLite for threaded application

I would suggest you to go for thread specific sqlite handles. This would make each thread operate in its own db connection handle. threadID = getthreadID(); if(threadIDHashList.find( threadID)== false) { //new thread,just add this threadID to list //create new DB connection and save it a