[miguelexplorer]

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”?

[miguelexplorer]

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.

[Author]

Posts