This looks like it should work fine.
The only thing that concerns me is this could be a very long loop
if something locks the table or there's an error that's not recoverable.
It would sit there forever retrying something that will never be fixed.
Some operations will cause the database to be reorganized and will
return schema errors when you run a prepared statement. You have to
re prepare your statement to get it to work. I'm not sure if that applies
to get_table though.
I've tried also executing the query "begine exclusive" before the "update",
and "commit" to end the entire routine, and the query that now returns the
exit code 5 (database locked) is "begin exclusive", I don't know if this
can be meaningful...
I see the calls to free the memory if it fails.
Do you free the memory used after success too?
Yes.
You might look through the source code for sqlite3_get_table().
You could put some debugging output there to help figure out
what's going wrong.
Ok, I try with the source code of the library!
Thank you very much for your help.
Laura
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
