You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mattab opened this issue
Aug 20, 2014
· 3 comments
Assignees
Labels
BugFor errors / faults / flaws / inconsistencies etc.CriticalIndicates the severity of an issue is very critical and the issue has a very high priority.
2014/08/20 10:18:03 [error] 21463#0: *26 FastCGI sent in stderr: "PHP message: Error in Piwik (tracker): Error query: SQLSTATE[HY000]: General error: 1364 Field 'location_browser_lang' doesn't have a default value In query: INSERT INTO piwik_log_visit (idvisitor, config_id, location_ip, custom_var_k1, custom_var_v1, config_browser_version, config_os, config_cookie, config_director, config_browser_name, referer_url, visit_total_searches, visit_total_actions, [...]
Could we set a default value to columns in Tracker to prevent this and future similar errors?
(set as Critical since it can lead to data loss for users with a Mysql configured in this way)
The text was updated successfully, but these errors were encountered:
@tsteur: I think that you could reproduce it by setting sql_mode=STRICT_TRANS_TABLES in mysql config (it's default config starting from 5.6) and for example replaying data from logs (the value is empty in that case).
BugFor errors / faults / flaws / inconsistencies etc.CriticalIndicates the severity of an issue is very critical and the issue has a very high priority.
Reported in forum:
2014/08/20 10:18:03 [error] 21463#0: *26 FastCGI sent in stderr: "PHP message: Error in Piwik (tracker): Error query: SQLSTATE[HY000]: General error: 1364 Field 'location_browser_lang' doesn't have a default value In query: INSERT INTO piwik_log_visit (idvisitor, config_id, location_ip, custom_var_k1, custom_var_v1, config_browser_version, config_os, config_cookie, config_director, config_browser_name, referer_url, visit_total_searches, visit_total_actions, [...]
Could we set a default value to columns in Tracker to prevent this and future similar errors?
(set as Critical since it can lead to data loss for users with a Mysql configured in this way)
The text was updated successfully, but these errors were encountered: