> So it means we can have mor than one valid db handle? Yes.
Pavel On Wed, Jul 7, 2010 at 9:29 AM, Lloyd <ll...@cdactvm.in> wrote: > So it means we can have mor than one valid db handle? > > Thanks, > Â Lloyd > > ----- Original Message ----- > From: "Pavel Ivanov" <paiva...@gmail.com> > To: "General Discussion of SQLite Database" <sqlite-users@sqlite.org> > Sent: Wednesday, July 07, 2010 6:40 PM > Subject: Re: [sqlite] sqlite3_step returns sqlite_busy > > >>> one thread is preparing an "INSERT" statement (It returns SQLITE_OK), >>> then it is executed using sqlite3_step. sqlite3_step returns an >>> SQLITE_BUSY! Is there any possibility for this? >> >> Sure. Preparing INSERT statement doesn't acquire any "write" locks on >> the database. It's executing the INSERT statement that acquires locks. >> So if while executing statement finds that it can't get the locks then >> sqlite3_step returns SQLITE_BUSY. And thread-safety is irrelevant >> here. >> >> >> Pavel >> > > > ______________________________________ > Scanned and protected by Email scanner > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
