I'm typically importing around 100,000 records at a time, so using 'SHOW WARNINGS' manually is no use - and I can't yet nail down a query that actually generates a warning anyway.
I can start the mysql client using -v, but as even at the lowest level or verbosity it always displays the query, and since my inserts are often 30k per record, it's just not practical to scan the output, plus it makes it go very slowly.
I've got log-warnings in my my.cnf file, and mysqld is definitely picking it up (adding it made log-warnings appear as set to 2, though I can't find any reference in the docs for what the values mean), but mysql is not logging any warnings at all.
I have log-error=/var/lib/mysql/mysql.err set in my.cnf, and again it's definitely being picked up by the server.
If it makes a difference, I'm using all InnoDB tables.
All I need is for warnings to be logged along with the query that caused it without having to log everything and trawl through it - what have I missed?!
Marcus -- Marcus Bointon Synchromedia Limited: Putting you in the picture [EMAIL PROTECTED] | http://www.synchromedia.co.uk
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
