Ticket #1790 (closed defect: fixed)

Opened 13 months ago

Last modified 13 months ago

toTopoGeom: ERROR: duplicate key value violates unique constraint "relation_layer_id_key"

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

Description

I don't know what's going on but a single call to toTopoGeom is triggering a "relation_layer_id_key" violation. The starting "relation" table is _empty_ 

select totopogeom('0105000000020000000102000000030000000000000000E065C002000000008056C001000000004065C0041AD965BE5554C002000000000064C0011AD965BE5554C001020000000200000000000000004065C0031AD965BE5554C00000000000E065C000000000008056C0', 'hextopo', 1);

Change History

Changed 13 months ago by strk

Ah, ok, clear... TopoGeo?_addLinestring returns a SET of primitive identifiers, and it's returning the same identifier more than once ...

Not sure if we should omit the duplicates from the TopoGeo?_addlinestring itself or from the caller...

Changed 13 months ago by strk

  • priority changed from medium to critical

Changed 13 months ago by strk

Oh, it's not even that, but toTopoGeom calling TopoGeo?_addLinestring two times, and the second time it gets the same result as the first time. At least we restrict the focus on toTopoGeom

Changed 13 months ago by strk

  • status changed from new to closed
  • resolution set to fixed

Fixed in r9675

Note: See TracTickets for help on using tickets.