@mgazdzik opened this Issue on March 28th 2014 Contributor

Recently we encountered problem with accurate lat/long storing when being passed by request parameter.

It looks like it's connected strictly with type of location_latitude and location_longitude columns.
Originally it's float and then error occurs. Altering it to decimal seems to solve problem.
How to reproduce:

  • on new Piwik instance set tracker to allow lat/long overriding:
    tracking_requests_require_authentication = 0

Then launch simpliest tracking request like:

and see in database what values are stored:

lat: 98.230003
long: -21.450001

On the other hand tracker debug show proper values.

After changing schema of log_visit table and launching next request, coordinates are stored properly (lat: 98.230000, long: -21.450000)

@mattab commented on March 31st 2014 Member

Thanks for the report!

@mattab commented on April 7th 2015 Member

This change requires a schema upgrade to ALTER the column types, which is currently blocked: No schema change allowed on log_visit nor log_link_visit_actions nor log_action tables #6953

@tsteur commented on August 8th 2016 Member
@mattab commented on September 23rd 2016 Member

@tsteur I went the easy route and simply cast the field to decimal. It's working good enough in our case.

@mattab commented on September 23rd 2016 Member

Done in #10543

This Issue was closed on September 23rd 2016
Powered by GitHub Issue Mirror