Re: [sqlite] Unexpected sqlite3_trace_v2 sqlite3_expanded_sql output.

2018-06-22 Thread Lodewijk Duymaer van Twist
Hi Clemens and Richard, I have not read the SQLITE_TRACE_STMT documentation well enough they where triggers containt in (X).. Thanks. Lodewijk Van: "Clemens Ladisch" Aan: "sqlite-users" Verzonden: Vrijdag 22 juni 2018 12:19:18 Onderwerp: Re: [sqlite] Unexpec

Re: [sqlite] Unexpected sqlite3_trace_v2 sqlite3_expanded_sql output.

2018-06-22 Thread Richard Hipp
On 6/22/18, Lodewijk Duymaer van Twist wrote: > > Is this normal explaiable behaviour or should I try to provide a repo? > It would be helpful if you could provide a repro. -- D. Richard Hipp d...@sqlite.org ___ sqlite-users mailing list

Re: [sqlite] Unexpected sqlite3_trace_v2 sqlite3_expanded_sql output.

2018-06-22 Thread Clemens Ladisch
Lodewijk Duymaer van Twist wrote: > I'm tracing queries that my application makes using sqlite3_trace_v2 and > sqlite3_expanded_sql in the callback. The application uses sqlite 3.22.0. > > At some point the software will call sqlite3_exec with the following > statement: > BEGIN TRANSACTION; >

[sqlite] Unexpected sqlite3_trace_v2 sqlite3_expanded_sql output.

2018-06-22 Thread Lodewijk Duymaer van Twist
Hi, I'm tracing queries that my application makes using sqlite3_trace_v2 and sqlite3_expanded_sql in the callback. The application uses sqlite 3.22.0. At some point the software will call sqlite3_exec with the following statement: BEGIN TRANSACTION; DELETE FROM call_lists WHERE id = 11;