You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem here is that in the map info pages we have access to the Map MapLayer set, so best option is to use the MapLayer title attribute.
If we want to use the Layer title attribute, we should consider to create a relation beween maps_maplayer and layers_layer. This would be useful also for maintaining referential integrity between the maps_maplayer/layers_layer combinations (now delegated to the layer post_delete_layer signal) and for many other db design reasons.
Such a decision would involve to store in layers_layer also remote layers, or have such a layer relation in maps_maplayer not mandatory (not null = true) for remote layers.
I can't see all the implication of doing that, but putting a foreign key in the MapLayer class means that Maps and Layers will be m2m related having MapLayer as an intermediate (through) class. Which makes sense to me.
No description provided.
The text was updated successfully, but these errors were encountered: