Andy,
On Tue, Feb 9, 2010 at 10:27 AM, andy knasinski a...@nrgsoft.com wrote:
I've used the general and slow query log in the past, but I am trying to
track down some queries from a compiled app that never seem to be hitting
the DB server.
My guess is that the SQL syntax is bad and never get
I've used the general and slow query log in the past, but I am trying
to track down some queries from a compiled app that never seem to be
hitting the DB server.
My guess is that the SQL syntax is bad and never get executed, but I
don't see any related queries in the general query log.
At 09:27 AM 2/9/2010, andy knasinski wrote:
I've used the general and slow query log in the past, but I am trying
to track down some queries from a compiled app that never seem to be
hitting the DB server.
My guess is that the SQL syntax is bad and never get executed, but I
don't see any
Unfortunately, I'm using a commercial application and trying to debug
as to why some data does and does not get updated properly.
On Feb 9, 2010, at 2:57 PM, mos wrote:
I do something like that in my compiled application. All SQL queries
are sent to a single procedures and executed there.
I'm not positive if the general log captures all invalid queries but
it does capture at least some.
I was asked the same question a few months back and checking to make
sure that manually issued invalid queries are logged (IIRC).
Could it be that the queries are never even making it to the
Am 09.02.2010 16:27, schrieb andy knasinski:
I've used the general and slow query log in the past, but I am trying to
track down some queries from a compiled app that never seem to be
hitting the DB server.
My guess is that the SQL syntax is bad and never get executed, but I
don't see any
