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
My workaround: modify the default restrictions of VARCHAR(20) like this:
mysql> ALTER TABLE matomo_log_visit MODIFY COLUMN config_browser_version VARCHAR(100);
Would be cool if such errors would not result in canceling the loading of the log files when doing ./console core:archive.
I wished that these these malformed entries would just be skipped and thus the indexing would go on. I really don't care of those bad log entries anyway.
I'm guessing that 60.989879960022535902747826837404505249 is not an official FireFox version number, but either way a long user input string shouldn't be able to cause a statement execution error.
STRICT_TRANS_TABLES mode would work around the issue but it could potentially cause problems for other applications that use the same database server. We could consider truncating tracker string values in the application code as another long term solution.
That should actually be fixed quite easily. The database column currently has a length of 20. So we could simply limit the version to 20 characters and throw away everything afterwards. So a simple substr($x, 0, 20) should fix this here: