Opened 3 years ago

Closed 3 years ago

#5026 closed defect (fixed)

DropTopology fires UPDATE triggers on topology layers

Reported by: strk Owned by: strk
Priority: medium Milestone: PostGIS 3.0.5
Component: topology Version: 2.0.x
Keywords: Cc:

Description (last modified by strk)

When an UPDATE trigger is set on a TopoGeometry layer, the DropTopology fires it, possibly failing. It should instead disable or drop triggers, I think.

Change History (8)

comment:1 by strk, 3 years ago

Summary: DropTopology fires DELETE triggers on topology layersDropTopology fires UPDATE triggers on topology layers

comment:2 by strk, 3 years ago

Description: modified (diff)

comment:3 by strk, 3 years ago

It's actually topology.DropTopoGeometryColumn firing the trigger. The function is invoked by DropTopology against all layers

comment:5 by Sandro Santilli <strk@…>, 3 years ago

In 27f44ecf/git:

Allow droppping TopoGeometry columns in presence of UPDATE triggers

References #5026 in main branch
Includes regression test

comment:6 by Sandro Santilli <strk@…>, 3 years ago

In 44deec4/git:

Allow droppping TopoGeometry columns in presence of UPDATE triggers

References #5026 in 3.1 branch (3.1.5dev)
Includes regression test

comment:7 by Sandro Santilli <strk@…>, 3 years ago

In 83b23368/git:

Allow droppping TopoGeometry columns in presence of UPDATE triggers

References #5026 in 3.0 branch (3.0.5dev)
Includes regression test

comment:8 by strk, 3 years ago

Milestone: PostGIS 3.2.0PostGIS 3.0.5
Resolution: fixed
Status: newclosed

I won't backport to branches lower than 3.0 3.0.5, 3.1.5 and main (3.2.0) have been fixed.

Note: See TracTickets for help on using tickets.