I have a big SQL script that has several dozen queries in it. It migrates data from one database to another. It seems to run without errors or warnings on my MAMP system and on the LAMP system that is our dev server. However, my co-worker is getting a lot of warnings and it results in critical tables being empty on his dev machine.
Running the script using the mysql command line, he gets a few errors with useful information but it also gives a lot of warnings that we can't seem to find more information about. Is there some way to view warnings? I've considered SHOW WARNINGS but by the time the script finishes all of the warnings in the early part of the script have been wiped by subsequent queries.
Here's an example of what he sees:
ERROR 1048 (23000): Column 'delivery_address_format_id' cannot be null
ERROR 1048 (23000): Column 'configuration_value' cannot be null
Query OK, 135314 rows affected (1.47 sec)
Records: 135314 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (3.42 sec)
Query OK, 638411 rows affected, 234 warnings (30.81 sec)
Records: 638411 Duplicates: 0 Warnings: 234
Query OK, 293451 rows affected (8.19 sec)
Records: 293451 Duplicates: 0 Warnings: 0
Query OK, 637 rows affected (0.03 sec)
Records: 637 Duplicates: 0 Warnings: 0
Query OK, 637 rows affected (0.03 sec)
Records: 637 Duplicates: 0 Warnings: 0
Query OK, 3882 rows affected (0.80 sec)
Records: 3882 Duplicates: 0 Warnings: 0
Query OK, 3889 rows affected, 1946 warnings (4.19 sec)
Records: 3889 Duplicates: 0 Warnings: 1946
I also suspect that these warnings might occur on my MAMP machine as well but I've looked in the mysql_log and can't seem to find any warnings there. No other logs appear to be active.
