You have pointers to the compiled SQL statements. You should be able to
track when the destination of those pointers changes. I haven't had the
need to do it, but it is where I would go if careful examination of the
code did not reveal the error.
JS
Eric Scouten wrote:
If it were easy to
I'm getting this error periodically when attempting to commit a transaction.
What I believe is happening is that my database abstraction layer has
lost track of one or more compiled statements that it created at some
earlier time. Is there any way to find out *what* transactions are still
You really need to post specific code snippets, you can't expect a
definitive solution including the complete diagnosis and corrected code
from an 11-word problem statement and then a 2-line guess as to the
cause. Please show your code. Others on this forum will help you. (I
lack the
If it were easy to boil down to a simple code snippet, I would have
happily done so. :-) Unfortunately, the error is probably caused
somewhere inside a relatively complex home-grown wrapper for SQLite and
is not easily distilled into something I can share here.
The question really boils down
Show your prepared statements and the code you are using to execute
them. There is always a simple cause to seemingly complex problems.
Bob
Eric Scouten wrote:
If it were easy to boil down to a simple code snippet, I would have
happily done so. :-) Unfortunately, the error is probably caused
Eric Scouten [EMAIL PROTECTED] wrote:
The question really boils down to can SQLite offer enough information
to help me diagnose the problem it's telling me I have?
Or to put it another way, this is essentially a memory leak problem.
SQLite obviously knows that I've lost track of one or
Eric Scouten wrote:
The question really boils down to can SQLite offer enough information
to help me diagnose the problem it's telling me I have?
Or to put it another way, this is essentially a memory leak problem.
SQLite obviously knows that I've lost track of one or more prepared
On Mon, Dec 12, 2005 at 06:55:24PM -0500, [EMAIL PROTECTED] wrote:
Eric Scouten [EMAIL PROTECTED] wrote:
Or to put it another way, this is essentially a memory leak problem.
SQLite obviously knows that I've lost track of one or more prepared
statements that haven't run to completion, it
Hello Eric,
I'd be inclined to throw it on the debugger and see what's going on.
If it's too complicated to debug, then maybe you need to re-think the
design. In my case, my code's littered with assertions and sanity
checks that kick out when I attempt to do something wrong. Sometimes
I'll
[EMAIL PROTECTED] wrote:
Eric Scouten [EMAIL PROTECTED] wrote:
The question really boils down to can SQLite offer enough information
to help me diagnose the problem it's telling me I have?
Or to put it another way, this is essentially a memory leak problem.
SQLite obviously knows that
10 matches
Mail list logo
