Opened 2 years ago
Last modified 16 months ago
#5284 new defect
Cannot pgtopo_import dumps with layers having renamed topogeom column
Reported by: | strk | Owned by: | strk |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS Fund Me |
Component: | topology | Version: | 3.3.x |
Keywords: | Cc: |
Description
When renaming a topogeometry column the constraint used to check its topology and layer identifiers keeps the old name but the pgtopo_import does not expect this, resulting in it not being able to disable the check. In turn, not disabling the check results in an exception thrown upon populating the layer.
Change History (5)
comment:1 by , 2 years ago
comment:2 by , 2 years ago
Milestone: | PostGIS 3.3.2 → PostGIS 3.3.3 |
---|
comment:3 by , 18 months ago
Milestone: | PostGIS 3.3.3 → PostGIS 3.4.0 |
---|
comment:4 by , 16 months ago
Note this ticket refers to renaming TopoGeometry columns using ALTER TABLE
.
Everything is fine if the RanameTopoGeometryColumn
function is used instead (#5286)
comment:5 by , 16 months ago
Milestone: | PostGIS 3.4.0 → PostGIS Fund Me |
---|---|
Summary: | Cannot restore topology dumps with layers having renamed topogeom column → Cannot pgtopo_import dumps with layers having renamed topogeom column |
Note:
See TracTickets
for help on using tickets.
NOTE: you need to have data in the layer in order for this problem to be reproducible (and as a work around you would need to edit the SQL dump to not create the constraint)