Bug: subdivisions edge case #16
Description
There is an edge case in which because there's a variable amount of subdivision information for a given IP/country, GeoIP data is stored inconsistently. Given that we only override GeoIP attributes if there are new attributes, consider this very typical flow:
- User connects from the US (where at least subdivision 1 is available).
- User connects from KE (where no subdivision information is available).
The user will then have a profile that looks like this, which is wrong:
- Country Name: Kenya
- City Name: Nairobi
- Subdivision 1 Code: VA
- Subdivision 1 Name: Virginia
We should probably override all GeoIP attributes when the country/city changes.