> I'm assuming that querying the same database using the same handle during a > "progress" callback would be a *bad* idea. Am I mistaken?
That would deadlock on handle's internal mutex or corrupt the handle if your SQLite is compiled without multi-threading support. Pavel On Wed, Nov 2, 2011 at 2:11 PM, Duquette, William H (318K) <william.h.duque...@jpl.nasa.gov> wrote: > I'm pretty sure I know the answer to this. > > Sqlite3 allows you to define a "progress" callback, which will be called > every so many byte-code instructions during a long-running query, so that you > can update a progress bar or like that. > > I'm assuming that querying the same database using the same handle during a > "progress" callback would be a *bad* idea. Am I mistaken? > > Will > -- > Will Duquette -- william.h.duque...@jpl.nasa.gov > Athena Development Lead -- Jet Propulsion Laboratory > "It's amazing what you can do with the right tools." > > _______________________________________________ > 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
