#3817 closed Bug (fixed)

visit_total_time set too low in database

Reported by: John.Deery Owned by: mattab
Priority: normal Milestone: 1.12 - The Great 1.x Backlog
Component: Core Keywords: out-of-bounds
Cc: Sensitive: no


While trying to import logs, I kept running across an error stating that the visit_total_time was out of range. Looking at the number trying to be inserted (65842) vs the column type (smallint, max of 65535), this is only 18.2 hours... crazy but some people might be on that long.

Changed the column to mediumint in my database to give a total of 16777215 (unsigned) seconds or 6.3 months

Change History (1)

comment:1 Changed 13 months ago by matt (mattab)

  • Owner set to mattab
  • Resolution set to fixed
  • Status changed from new to closed

In b4201236cfee91cb2742d06a4e876b53f737f28d:

Fixes #3817 Capping visit_total_time

Thanks for the report!

PS: this visit is most likely a bot or browser with auto refresh

Note: See TracTickets for help on using tickets.