[sqlite] sqlite3_prepare() and multithreading

Is it ok to call sqlite3_prepare() for a statement using the sqlite3 struct owned by thread A, and then run the actual query with sqlite3_step() and sqlite3_finalize() using the [different] sqlite3 struct owned by thread B? (Assume however that both sqlite3 structs were opened to the same

[sqlite] What does this code do?

In sqlite3VdbeRecordCompare() /* Read the serial types for the next element in each key. */ idx1 += sqlite3GetVarint32([idx1], _type1); if( d1>=nKey1 && sqlite3VdbeSerialTypeLen(serial_type1)>0 ) break; idx2 += sqlite3GetVarint32([idx2], _type2); if( d2>=nKey2 &&

[sqlite] Re: upgrade from 2 to 3

Nevermind, it seems I have found the cause, I was doing: sqlthread->exec("PRAGMA synchronous = 0;",NULL,NULL); sqlthread->exec("PRAGMA cache_size = 4000;",NULL,NULL); but changing it to this has sorted the problem out: sqlthread->exec("PRAGMA

[sqlite] upgrade from 2 to 3

I've just upgraded my program from using v2.8.16 of sqlite to using v3.2.1 of sqlite. So I've change the wrapper class that I was using to use the new prepare() instead of compile() etc. The problem I have is that my program is now running slower - a lot slower, as in one fiftieth of its previous

[sqlite] Thanks

Just a quick note letting you know that sqlite is working great here. Thanks for making such a wonderful tool available to the world. Only bump that I hit was that python-sqlite 1.0.1 automatically decodes BLOBs, which did not jive with inserted MIME enocede data using `sqlite`. Switching to