forums › forums › SQLyog › Using SQLyog › Unable To See Full List Of Errors + Warnings, Sqlyog.err Is Empty
- This topic is empty.
-
AuthorPosts
-
-
July 30, 2015 at 7:51 am #13397miguelexplorerMember
Hi all,
I’m on SQLyog community v12.12 (32 bit).
I’m importing raw .csv data into one of my tables, the raw data is still a work-in-progress and hence sketchy.
SQLyog says there are over 7000 warnings, thats okay because I know the raw data is at fault.
Most of the warnings are due to incorrect data types and empty values. But there is nothing I can do about it until the raw data guy fixes up his act. I wish to see the full error log to troubleshoot other things like truncated data or genuine data type errors.
However clicking “Show Warnings” only shows me the first 30 or so entries. This severely limits my ability to troubleshoot. I am essentially blind beyond the first 30 warnings.
The error dump file is always 0kb as well.
Question: How can I see the full list of errors + warnings?
I have poked around the options and preferences but could not find anything relevant.
I also tried my old friend Google but with no success.
Any ideas?
Please note: I’m aware my .csv raw data is sketchy, unfortunately there’s nothing much I can do about it. I hope it isn’t too much to be able to see a full error dump!
Thanks in advance!
-
July 30, 2015 at 11:50 am #35451peterlaursenParticipant
Have you tried simply to execute “SHOW WARNINGS;” from the editor after import? Does this also truncate?
-
July 30, 2015 at 12:01 pm #35452peterlaursenParticipant
You may also execute “SHOW VARIABLES LIKE ‘warning_count’;” after the import. (refer https://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#sysvar_warning_count).
The purpose of all this is to check how many warnings the server records and sends.
-
July 30, 2015 at 8:04 pm #35453miguelexplorerMember
Hi Peter,
Thanks for the speedy reply.
I was not aware of the “SHOW WARNINGS;” command – I’m clearly a SQL newbie here haha
Unfortunately the command result was also truncated, I checked and it was truncated at the exact same row as the “Show warnings” button and corresponding GUI display as shown in the screenshot earlier.
After executing the “SHOW WARNINGS;” command, from the “Messages” tab, I saw that “64 row(s)” were affected, a very suspicious binary number.
Curiously, running the “SHOW VARIABLES LIKE ‘warning_count’;” command returned a value of zero.
I re-imported again producing the same number of warnings and errors and ran the command again, still zero.
-
July 31, 2015 at 10:12 am #35454peterlaursenParticipant
1) If SHOW WARNING truncates it seems like it is the server that does. It probably has a fixed length buffer. We wll check this
2) I also noticed yesterday that ‘warning_count’ always seems to return “0”. I posted to bugs.mysql.com about this already http://bugs.mysql.com/bug.php?id=77883
-
July 31, 2015 at 10:26 am #35455peterlaursenParticipant
I now also posted this http://bugs.mysql.com/bug.php?id=77902
-
July 31, 2015 at 10:54 am #35456peterlaursenParticipant
Already had a reply in the last bug report.
Please see https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_max_error_count
.. and execute “SHOW VARIABLES LIKE ‘max_error_count’;”. What does this return?
-
August 1, 2015 at 8:42 am #35457miguelexplorerMember
Wow Peter, thank you for going the extra mile with all that legwork, I am grateful.
“SHOW VARIABLES LIKE ‘max_error_count’;” returns 64 for me.
For the benefit of other SQL newbies who might be following:
If you wish to increase the “max_error_count” system variable, execute “SET max_error_count=x;” (acceptable values range from 0 – 65535)
Documentation: https://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#sysvar_max_error_count
This will help to minimise any truncation of future warning reports.
My immediate issue of viewing the full warning log is now resolved. However, my error dump file is still always zero kb. Is this perhaps related to “warning_count”?
-
August 2, 2015 at 10:31 am #35458peterlaursenParticipant
I have already told that the sqlyog.err file records internal SQLyog errors only and not MySQL/server errors. Teherver logs its errors 8and optionally warnings) in its own error log – refer https://dev.mysql.com/doc/refman/5.6/en/error-log.html
-
-
AuthorPosts
- You must be logged in to reply to this topic.