RE: [sqlite] sqlite3_step() returning SQLITE_DONE for query that should return results

OK, I'm an idiot. I apologize if anybody wasted their time on this, it turned out to be something stupid I was doing. (An unrelated bug was changing the index value I was looking up, and though I thought I turned transactions off for this operation, it was turned off for the earlier but not

Re: [sqlite] Quick question about multithread and SQLITE_BUSY/SQLITE_LOCKED in 3.5.4

Using read and write locks around your statements gives you protection and lets you compile without thread safe so that Sqlite does not use internal mutexes as much for synchronization saving you considerable overhead as well as avoiding the logic necessary to handle BUSYs from Sqlite and

Re: [sqlite] Quick question about multithread and SQLITE_BUSY/SQLITE_LOCKED in 3.5.4

Am 19.1.08 um 03:13 schrieb [EMAIL PROTECTED]: OK I figured out SQLITE_THREADSAFE=0 for the second question... And it seems the answer for the first question is yes, but if you know a simpler way please share it with us, thanks! You could use a read-write mutex to serialize access to your

[sqlite] fts3 - primary key doesn't seem to do anything

SQLite version 3.5.4 sqlite> create virtual table foo using fts3(content, id primary key); sqlite> insert or replace into foo values('anything', 1); sqlite> insert or replace into foo values('anything', 1); sqlite> insert or replace into foo values('anything else', 1); sqlite> select * from foo;

[sqlite] fts3 - "SQL logic error or missing database" on all match words negated

SQLite version 3.5.4 sqlite> create virtual table foo using fts3; sqlite> insert into foo values('anything'); sqlite> select * from foo where foo match '-all -words -are -negated'; SQL error: SQL logic error or missing database Yeah, I know it's not really a useful thing to search for nothing but

[sqlite] RE: Assertion for Virtual Table INSERT

I tracked down the cause of this problem to an experimental change made locally to SQLite. :-( All is well with SQLite! :-) Mark > -Original Message- > From: Evans, Mark (Tandem) > Sent: Friday, January 18, 2008 3:45 PM > To: sqlite-users@sqlite.org > Subject: [sqlite] Assertion for

RE: [sqlite] Slow query on one machine

I can't do anything like that as it is a machine of a customer and I have no access to it. Just wondering what possibly could explain such a difference. The relevant thing is that are load of queries coming after this and they are all fine. So it specific to that particular table at that

Re: [sqlite] Slow query on one machine

On Jan 18, 2008 3:32 PM, RB Smissaert <[EMAIL PROTECTED]> wrote: > The application > that runs this is exactly the same on both machines. The slow machine is > actually slightly slower specification wise, but that can't explain the huge > differences in timings. > Have you run spinrite ( a disk