Updating a database feature source clears the tile cache

[zspitzer]

When a database feature source is updated ( ie password host etc ) any associated tile caches get purged, when the featuresource isn't in one of the cached layers.

[MaksimS]

Not only that, it should traverse base layers and associated feature sources to see whether they get affected by current change (taking into account resource visibility, scale, etc). If not, tile cache should not be cleared. Since it takes so much time and effort (MG crashing) to actually build tile cache - it's really worth preserving it's contents as much as possible.

[leodai]

code fix for this defect

[leodai]

In this fix code, we add a check to see whether the related layer of the featuresource which is updated is in a base layer of the Map.If not, the tile cache won't be cleared.

[jbirch]

Was this fix (minus the project file changes) applied? Seems like a valuable addition.