Geometry conflict checking to background #202

New Issue

mpeltriaux · 2022-09-13T08:08:03+02:00

mpeltriaux commented

2022-09-13 08:08:03 +02:00

Status quo

On each save() call of a Geometry object, we perform a check for geometry conflicts, especially intersections with other entries:


    def save(self, *args, **kwargs):
        super().save(*args, **kwargs)
        self.check_for_conflicts()

Now, if the given geometry is rather big and a lot of intersected geometries have been detected, this second step may take a few seconds (on very, very large geometries).

Enhancement

Refactor check_for_conflicts() to a celery background task, so it will be calculated in the background and the user does not need to wait for a result on this operation.

# Status quo On each `save()` call of a Geometry object, we perform a check for geometry conflicts, especially intersections with other entries: ```python def save(self, *args, **kwargs): super().save(*args, **kwargs) self.check_for_conflicts() ``` Now, if the given geometry is rather big and a lot of intersected geometries have been detected, this second step may take a few seconds (on very, very large geometries). # Enhancement Refactor `check_for_conflicts()` to a celery background task, so it will be calculated in the background and the user does not need to wait for a result on this operation.

mpeltriaux added the

enhancement

label 2022-09-13 08:08:03 +02:00

mpeltriaux self-assigned this 2022-09-13 08:08:03 +02:00

mpeltriaux referenced this issue

2022-09-15 12:13:06 +02:00

202 Geometry conflict checking to background #204

mpeltriaux commented

2022-09-15 12:13:27 +02:00