Hi there,
When we use our custom SQLite function function_sparql_regex (lower in
this E-mail) together with bound values for the argvs of the function,
then sqlite3_reset nor sqlite3_clear_bindings are clearning the auxdata.
This makes it impossible to pass the regex as a sqlite3_bind_text (the
Philip Van Hoof s...@pvanhoof.be wrote:
When we use our custom SQLite function function_sparql_regex (lower in
this E-mail) together with bound values for the argvs of the function,
then sqlite3_reset nor sqlite3_clear_bindings are clearning the
auxdata.
This makes it impossible to pass
I have some questions on the usage of sqlite3_reset (or
sqlite3_finalize) after sqlite3_step.
In the legacy interface I use sqlite3_reset after sqlite3_step to obtain
a more specific error code for SQLITE_ERROR (to be able to detect schema
errors and automatically reprepare the statement,
Hi,
I prepare a statement in my constructor's class. Later, when I need data
from that statement, I bind all variables and step trough the results. Is it
necessary to reset the statement when I need other data from that statement
or is this done automatically when I bind new variables?
Best
Hi,
if i understand you right, the bound variables occur in your where class.
If you want to start stepping through your result set with newly bound
variables, you have to reset the statement first.
You can also reset the statement, put new values into the already bound
variables and start
Correct. Thanks for your help!
Merijn
-Oorspronkelijk bericht-
Van: Martin Engelschalk [mailto:[EMAIL PROTECTED]
Verzonden: donderdag 23 maart 2006 12:13
Aan: sqlite-users@sqlite.org
Onderwerp: Re: [sqlite] Sqlite3_reset needed?
Hi,
if i understand you right, the bound variables
Merijn Vandenabeele [EMAIL PROTECTED] wrote:
Hi,
I prepare a statement in my constructor's class. Later, when I need data
from that statement, I bind all variables and step trough the results. Is it
necessary to reset the statement when I need other data from that statement
or is this done
Hi Richard,
You should be in the habit of calling sqlite3_reset() on each query
as soon as that query finishes. Otherwise the query *might* leave a
read-lock on the database file and thus prevent subsequent write
operations for working correctly.
What about if one just uses sqlite3_exec ?
CARTER-HITCHIN, David, FM [EMAIL PROTECTED] wrote:
Hi Richard,
You should be in the habit of calling sqlite3_reset() on each query
as soon as that query finishes. Otherwise the query *might* leave a
read-lock on the database file and thus prevent subsequent write
operations for working
Hi!
I have a couple of questions regarding the sqlite3_reset function.
Does sqlite3_reset free all the locks on the database?
Do I actually need to call sqlite3_reset directly after sqlite3_step is
done to free database locks?
Or does sqlite3_step free the locks automatically?
Thanks in advance!
10 matches
Mail list logo