Allow to use natural primary/foreing keys for geoname objects.

[cezio]

Current default model implementation relies on a sequence as a primary key value for each model. This leads to a situation where two sibling deployments may have different IDs for the same objects, when cities_lights import was run in a different time frame or with different order of objects imported. An interchange of other data that relies on cities_light models between those two may be difficult in such situation.

A solution would be to support natural primary/foreign keys in models and use them in dump/load commands: https://docs.djangoproject.com/en/3.0/topics/serialization/#natural-keys

[dwasyl]

+1 This would be really handy

[cezio]

Actually, wouldn't it be more feasible to use geoname_id as the primary key in each model? It is unique already (locally and from the data source), and it's portable between datasets.

[marianoeramirez]

@cezio @dwasyl

I think that change the primary key will be something out of scope, for the complexity to do the migration for all the users of this library.

But I like the idea of using natural keys to dump and load the data into the system. On the development branch, you can test initial support of this feature. The feedback is appreciated!!

[marianoeramirez]

The solution to this problem is already live on version 3.9.

Still left write the documentation about this but closing this ticket for now.