On 15 Jan 2016, at 4:20pm, Olivier Mascia wrote:
> I'm only left with the case of a row returning query which the programmer
> would not want to step() up to the end. In this case, it is very reasonable
> to have the programmer think of "freeing" the query in some way through
> either the
Richard, Simon,
> Le 15 janv. 2016 ? 16:30, Richard Hipp a ?crit :
>
>> But the finalize of a
>> statement (using the C++ wrapper we build for our use over C SQLite API) is
>> currently differed until another prepare is done using the same Statement
>> object, or until the Statement object goes
> Le 15 janv. 2016 ? 13:08, Hick Gunter a ?crit :
>
> I think you may mean "database connection" instead of "statement handle".
>
> When you are finished with processing a statement, you should either reset
> (if you intead to use it again later) or finalize it. Otherwise SQLite must
>
On 15 Jan 2016, at 3:18pm, Olivier Mascia wrote:
> Be sure I'm not reusing any statement handle without finalizing it. No
> leaks, we have a checker in place to detect. But the finalize of a statement
> (using the C++ wrapper we build for our use over C SQLite API) is currently
> differed
> Le 15 janv. 2016 ? 11:54, Olivier Mascia a ?crit :
>
> What are the circumstances leading to:
>
> int status = sqlite3_wal_checkpoint_v2(conn, "main",
> SQLITE_CHECKPOINT_PASSIVE, 0, 0);
>
> returning SQLITE_LOCKED immediately?
>
>
> It looks like that the simple fact of having a select
sqlite-users-bounces at mailinglists.sqlite.org
[mailto:sqlite-users-bounces at mailinglists.sqlite.org] Im Auftrag von Olivier
Mascia
Gesendet: Freitag, 15. J?nner 2016 12:18
An: SQLite mailing list
Betreff: Re: [sqlite] sqlite3_wal_checkpoint_v2() returning SQLITE_LOCKED: in
what circumstances?
> L
Dear all,
What are the circumstances leading to:
int status = sqlite3_wal_checkpoint_v2(conn, "main", SQLITE_CHECKPOINT_PASSIVE,
0, 0);
returning SQLITE_LOCKED immediately?
It looks like that the simple fact of having a select statement prepared, then
ran, but not yet finalized, on that
On 1/15/16, Olivier Mascia wrote:
> But the finalize of a
> statement (using the C++ wrapper we build for our use over C SQLite API) is
> currently differed until another prepare is done using the same Statement
> object, or until the Statement object goes out of scope (destructor).
That's a
8 matches
Mail list logo
