I have an old application that started after upgrading from MySQL 5.0 to 5.1.
Few studies have shown that this is due to "strict mode", which prevents the insertion of certain types of "invalid" values that previously were simply automatically converted to something reasonable.
I tried SET @@SESSION.sql_mode = ''and SET @@GLOBAL.sql_mode = ''but I still get the error.
Also tried to comment sql_modeon my.ini.
Is there a stronger, “nuclear” opportunity to fix this?
source
share