Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Work-around for #6834 (Numeric value out of range: 1264 Out of range value for column 'visit_total_actions') #10064

Closed
rysiekpl opened this issue Apr 17, 2016 · 3 comments
Closed

Work-around for #6834 (Numeric value out of range: 1264 Out of range value for column 'visit_total_actions') #10064

rysiekpl opened this issue Apr 17, 2016 · 3 comments
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.

Comments

@rysiekpl
Copy link

Since comments seem to be disabled on the original issue, submitting a new issue to signal the need for a work-around. From the original issue comment thread:

I think best solution would be to change the type of the field to UNSIGNED MEDIUMINT

Is performing this change manually on our Piwik 2.16.1 install safe? Obviously it should not break anything for the time being, but will it be compatible with future schema changes? Will the schema upgrade script work in a situation where one of the changes has already been done?

Or is there any other workaround?
@sgiehl
Copy link
Member

sgiehl commented Apr 17, 2016

will be fixed by #9565 in Piwik 3.0

Doing manual changes to the log_visit table might cause problems, as changes to this table are done automatically based on the definitions in the column files. See https://github.com/piwik/piwik/blob/master/plugins/Actions/Columns/VisitTotalActions.php#L21

@rysiekpl
Copy link
Author

Great. Still, we are hitting this error in our Piwik instance and it stops us from loading logs -- which we depend on very much. Is there a possible work-around?

We have a testing environment that mirrors production, so we can test stuff without danger, if that helps.

@tsteur
Copy link
Member

tsteur commented Apr 18, 2016

Actually a manual schema change should do the trick as we do not verify which check is actually set (as different SQL versions could report it differently etc). If you update at some point to Piwik 3 it might perform another schema change for that column but this change will just fix it as well.

In Piwik 3 we fixed it here #10002 by setting the column type to INT(11) UNSIGNED NOT NULL. I suggest you do the same see #9565

@tsteur tsteur closed this as completed Apr 18, 2016
@tsteur tsteur added the duplicate For issues that already existed in our issue tracker and were reported previously. label Apr 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tsteur @sgiehl @rysiekpl