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

Numeric value out of range: 1264 Out of range value for column 'visit_total_actions' at row 1 In query #6834

Closed
mattab opened this issue Dec 9, 2014 · 6 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Dec 9, 2014

This was reported in the forums:

Following my upgrade to the latest version, I am getting the following problem when importing logs.

2014/12/06 11:28:11 [error] 2848#0: *29 FastCGI sent in stderr: "PHP message: Error in Piwik (tracker): 
Error query: SQLSTATE[22003]: Numeric value out of range: 
1264 Out of range value for column 'visit_total_actions' at row 1 In query: 
UPDATE piwik_log_visit SET idvisitor = ?, visit_total_time = ?, visit_last_action_time = ?, visit_exit_idaction_url = ?, visit_total_actions = visit_total_actions + 1 , custom_var_k1 = ?, custom_var_v1 = ? WHERE idsite = ? AND idvisit = ? Parameters: array ( 0 => '&▒▒▒▒E▒', 1 => 4852, 2 => '2014-11-30 19:18:36', 3 => 277470, 4 => 'Not-Bot', 5 => 'Mozilla/5.0 (Windows NT 6.3; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0', 6 => 72, 7 => 21276112, )
@mattab mattab added the Bug For errors / faults / flaws / inconsistencies etc. label Dec 9, 2014
@mattab mattab modified the milestones: Piwik 2.10.0 , Piwik 2.11.0 Dec 9, 2014
@mattab
Copy link
Member Author

mattab commented Dec 9, 2014

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

@mattab
Copy link
Member Author

mattab commented Jan 8, 2015

let's make this change only if there is another "Major DB schema change". There's no point making an upgrade "heavy schema change upgrade" just for fixing this bug

@mattab mattab modified the milestones: Piwik 2.12.0, Piwik 2.11.0 Jan 8, 2015
@mattab
Copy link
Member Author

mattab commented Feb 23, 2015

Moving to next milestone because we are still waiting for resolution of #6953

@mattab mattab modified the milestones: Piwik 2.13.0, Piwik 2.12.0 Feb 23, 2015
@mnapoli
Copy link
Contributor

mnapoli commented Mar 25, 2015

#6953 is assigned to 2.13.0 so this issue should be moved to the next milestone.

@mattab mattab modified the milestones: Short term, Piwik 2.13.0 Mar 25, 2015
@mattab
Copy link
Member Author

mattab commented Sep 11, 2015

moving to 3.0.0 where will apply big schema changes

@mattab mattab modified the milestones: Short term, 3.0.0 Sep 11, 2015
@mattab mattab modified the milestones: 3.0.0-b1, 3.0.0 Oct 1, 2015
@mattab mattab added the Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. label Oct 1, 2015
@tsteur
Copy link
Member

tsteur commented Sep 13, 2016

I think this was resolved in #10002 and seems to be a duplicate of #9565 . Please reopen if not.

@tsteur tsteur closed this as completed Sep 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Projects
None yet
Development

No branches or pull requests

3 participants