lite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Marcus Grimm
Sent: Monday, April 13, 2009 7:21 PM
To: 'General Discussion of SQLite Database'
Subject: Re: [sqlite] step() fails with SQLITE_BUSY after BEGIN
EXCLUSIVETRANSACTION
Mario,
I'm sorry but I'm running ou
Mario,
I'm sorry but I'm running out of ideas... I can only
repeat that sqlite works well with this kind of approach.
I'm using it in a database server without a problem so far
and there I use the exclusive mode to block the threads.
However, when I started using sqlite for this I also run
into
Marcus
thanks for your suggestions. I have of course checked the obvious things
before posting here.
Both the BEGIN EXCLUSIVE and the COMMIT return SQLITE_OK.
Each thread opens its own db handle with sqlite_open and operates on it.
These are completely isolated, they don't know about each
I have no idea why it doesn't work in that way, it used to
in my application. however, just a few points:
maybe your BEGIN wasn't successful and you didn't realize ?
maybe you run the INSERT on a DB handle that was not the one
that invoked the BEGIN ?
maybe your COMMIT wasn't successful and you
Hi, Dave
I have read your post. I have also read many of the recent archived posts,
and googled the web for hints. I'm at a loss here.
The fun thing is that my wrapper class (which I use for a while now in
non-MT environments) allows me to track most of what's going on in SQLite.
And even that
5 matches
Mail list logo
