[sqlite] sqlite3_trace not showing all steps?

On Wed, Oct 07, 2015 at 10:30:53AM -0400, Richard Hipp wrote: > On 10/7/15, Aki Tuomi wrote: > > > > Abusing bit more it would seem that when it's not logging, it's going thru > > sqlite3Reprepare and doing a rerun. Wonder if this causes the logging be > > suppressed? See http://p.ip.fi/bt6b > >

[sqlite] sqlite3_trace not showing all steps?

On Wed, Oct 07, 2015 at 04:58:10PM +0300, Aki Tuomi wrote: > On Wed, Oct 07, 2015 at 09:35:54AM -0400, Richard Hipp wrote: > > On 10/7/15, Aki Tuomi wrote: > > > > > > Is there any way to see whether sqlite3_trace has been attached to a > > > particular connection? > > > > > > > Perhaps run

[sqlite] sqlite3_trace not showing all steps?

On Wed, Oct 07, 2015 at 09:35:54AM -0400, Richard Hipp wrote: > On 10/7/15, Aki Tuomi wrote: > > > > Is there any way to see whether sqlite3_trace has been attached to a > > particular connection? > > > > Perhaps run "sqlite3_exec(db, "SELECT 'trace-test';",0,0,0)" and see > if you get a trace

[sqlite] sqlite3_trace not showing all steps?

On Wed, Oct 07, 2015 at 08:42:47AM -0400, Richard Hipp wrote: > On 10/7/15, Aki Tuomi wrote: > > Hi! > > > > We use SQLite3 in PowerDNS as one backend and we have implemented query > > logging using sqlite3_trace. Unfortunately it seems that it does not log > > all executed queries, despite being

[sqlite] sqlite3_trace not showing all steps?

Hi! We use SQLite3 in PowerDNS as one backend and we have implemented query logging using sqlite3_trace. Unfortunately it seems that it does not log all executed queries, despite being turned on. We see one or two queries but most go unlogged. I tried to generate a minimal example to see if it

[sqlite] sqlite3_trace not showing all steps?

On 10/7/15, Aki Tuomi wrote: > > Abusing bit more it would seem that when it's not logging, it's going thru > sqlite3Reprepare and doing a rerun. Wonder if this causes the logging be > suppressed? See http://p.ip.fi/bt6b > Try the patch below to see if it makes a difference: Index: src/vdbe.c

[sqlite] sqlite3_trace not showing all steps?

On 10/7/15, Aki Tuomi wrote: > > Is there any way to see whether sqlite3_trace has been attached to a > particular connection? > Perhaps run "sqlite3_exec(db, "SELECT 'trace-test';",0,0,0)" and see if you get a trace callback? -- D. Richard Hipp drh at sqlite.org

[sqlite] sqlite3_trace not showing all steps?

On 10/7/15, Aki Tuomi wrote: > Hi! > > We use SQLite3 in PowerDNS as one backend and we have implemented query > logging using sqlite3_trace. Unfortunately it seems that it does not log > all executed queries, despite being turned on. We see one or two queries > but most go unlogged. > > I tried

Re: [sqlite] sqlite3_trace() threadsafe

Am 2012-09-05 18:53, schrieb esum: Thank you so much for all help. I really appreciate it. /"All the same, I'm guessing that http://www.sqlite.org/src/info/39f763bfc0will fix your problem."/ I gave this new src code from the src tree a shot, but I seem to be getting the same behavior.

Re: [sqlite] sqlite3_trace() threadsafe

Thank you so much for all help. I really appreciate it. /"All the same, I'm guessing that http://www.sqlite.org/src/info/39f763bfc0will fix your problem."/ I gave this new src code from the src tree a shot, but I seem to be getting the same behavior. Interestingly though, I tried enforcing my

Re: [sqlite] sqlite3_trace() threadsafe

On Tue, Sep 4, 2012 at 4:50 PM, esum wrote: > I see what you are suggesting. However, I do not see a schema change going > on in the middle of the code that would cause sqlite3_step () to reprepare > the statement. > All the same, I'm guessing that

Re: [sqlite] sqlite3_trace() threadsafe

On 4 Sep 2012, at 7:14pm, esum wrote: > I am getting odd results when I do a simple test such as doing a couple of > inserts to different tables from 4 threads. Some sql statements appear to > be printed twice or more when they should only be printed once. The sql >

Re: [sqlite] sqlite3_trace() threadsafe

I see what you are suggesting. However, I do not see a schema change going on in the middle of the code that would cause sqlite3_step () to reprepare the statement. The database that I am working with utilizes sqlite's shared-cache mode for all connections to it along with the

Re: [sqlite] sqlite3_trace() threadsafe

On Tue, Sep 4, 2012 at 2:14 PM, esum wrote: > Is sqlite3_trace () > threadsafe? Yes. > Is there a reason that the same sql statement is being passed > twice to the callback function when it is really only executed once? Probably this is due to a schema change.

[sqlite] sqlite3_trace() threadsafe

Hi, I am using sqlite version 3.7.13 in a multi-threaded application. In this application, multiple connections to the same database are established, and every connection has the sqlite tracer attached to it with the sqlite3_trace () function. I use the same callback function in each of the

[sqlite] sqlite3_trace active on FTS3 (sub-)statements, pathologically bad at stringifying (segment) BLOBs (quasi-enhancement request)

In our Mozilla debug builds we use sqlite3_trace to expose the SQL statements that are invoked via our PR_LOG logging subsystem. This usually works out well but the trace also catches FTS3's statements in its net. During a segment merge, a segment in a Thunderbird FTS3 table can easily be

Re: [sqlite] sqlite3_trace

Boy I was off on that one. The stmt is not going to help my case. The users context that is already there can help me. Sorry, -Alex On Wed, Aug 20, 2008 at 8:52 PM, Alex Katebi <[EMAIL PROTECTED]> wrote: > Hi All, > > I am using the sqlite3_trace to track down a bug. It is lacking a vital >

[sqlite] sqlite3_trace

Hi All, I am using the sqlite3_trace to track down a bug. It is lacking a vital information that is needed for tracing. The stmt handle is necessary in order to identify related statements. Notice the sqlite3_stmt that I have added below. void *sqlite3_trace(sqlite3*, void(*xTrace)(void*,const

Re: [sqlite] sqlite3_trace args?

Clear's things up. Thanks! - Kervin Quoting Christian Smith <[EMAIL PROTECTED]>: > On Wed, 6 Oct 2004 [EMAIL PROTECTED] wrote: > > > > >Thanks, > > > >Question, why does transactions report the error whilst CREATE > >on its own returns success but secretly fails? > > Because the actual

Re: [sqlite] sqlite3_trace args?

On Wed, 6 Oct 2004 [EMAIL PROTECTED] wrote: > >Thanks, > >Question, why does transactions report the error whilst CREATE >on its own returns success but secretly fails? Because the actual CREATE succeeded. The COMMIT couldn't happen because of the ongoing VM from the non-finalized VM, hence the

Re: [sqlite] sqlite3_trace args?

Thanks, Eventually I did get into the source. I was just hoping there was more authorative documenation out there, other than my interpretation of what the source may be doing. Transactions solved the problem, thanks. Funny, it didn't help till I put the transaction BEGIN, CREATE, and COMMIT

Re: [sqlite] sqlite3_trace args?

On Tue, 5 Oct 2004 [EMAIL PROTECTED] wrote: > > >Hello, > >I am trying debugging my application ( Sqlite reports no errors >after a CREATE query, but the table does not exist ). Have you done this in a transaction? Check you haven't issued a BEGIN statement, and/or COMMIT the current

[sqlite] sqlite3_trace args?

Hello, I am trying debugging my application ( Sqlite reports no errors after a CREATE query, but the table does not exist ). I'd like to use sqlite3_trace() function, but the documentation does not have the expected args, neither does the mail archives. Can someone explain to me briefly what