-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
P Kishor wrote:
> I have a rather opaque application that is calling my db. Is there
> something I can turn on in SQLite that will log all the statements
> executed against it?
If you are using Linux then you can use the ltrace program to trace
calls
> You can't create a trigger on a select. Only insert, delete, and
> update statements can fire a trigger.
True. Though now that you mention it, it would obviously be useful to
be able to trigger from a select.
>> CREATE TRIGGER log_foo
>> INSTEAD OF SELECT ON view_bar
>> INSERT INTO log_fo
P Kishor wrote:
>
> Ok. Let's translate the above in English (for my sake).
>
> Keep in mind the following as you answer the above -- I have SQLite
> compiled already; I can recompile it. I have an application that I
> can't change that is calling SQLite through its own interface. I want
> to log
On 4/18/08, Dennis Cote <[EMAIL PROTECTED]> wrote:
> P Kishor wrote:
>
> > I have a rather opaque application that is calling my db. Is there
> > something I can turn on in SQLite that will log all the statements
> > executed against it?
> >
> >
>
> You can use sqlite3_trace() to register a callba
P Kishor wrote:
> I have a rather opaque application that is calling my db. Is there
> something I can turn on in SQLite that will log all the statements
> executed against it?
>
You can use sqlite3_trace() to register a callback that is passed each
SQL statement as it is executed. Your callback
I have a rather opaque application that is calling my db. Is there
something I can turn on in SQLite that will log all the statements
executed against it?
--
Puneet Kishor
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-
6 matches
Mail list logo