region and city fields in DB

roball - March 14, 2009 - 15:17
Project:GeoUser
Version:6.x-1.7-beta7
Component:Code
Category:support request
Priority:normal
Assigned:Unassigned
Status:active
Description

I have noticed that along with each user's IP address, MySQL's geouser table also stores the country, region and city. Today, I have updated the GeoLiteCity.dat database file from the October 2008 to the current March 2009 version. One of our users' city (Leeds in the UK) has been reported incorrectly by the October 2008 version as Castleford and now again incorrectly as Beverley. However, the database table still has the original city (Castleford) associated to that user's (same) IP address.

Thus, my question is, why does your module not read the region and city fields from the DB when displayed on a user's profile page? It seems that instead region information is always fetched freshly based on the stored IP.

 
 

Drupal is a registered trademark of Dries Buytaert.