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 database? Kyong
On Tue, Feb 9, 2010 at 2:05 PM, andy knasinski <a...@nrgsoft.com> wrote: > 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 trap any errors and log >> the SQL in a table along with the error message. This is useful to determine >> if someone is trying to break into the database (sql injection). Having a >> central procedure to execute all queries is paramount in controlling and >> capturing errors. I can also unplug and plug in a different database engine >> quite easily rather than hunting down all direct calls to the database. I >> also don't have to worry about trapping errors throughout the application. >> It's all done at one central point. >> >> I've been doing it this way for 5 years and would never start a large >> application without it. > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql?unsub=kykim...@gmail.com > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
