Opened 6 months ago

Closed 5 months ago

#4929 closed enhancement (fixed)

GetRingEdges silently returns a null row when passed an unexistent topology name

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

Description

I think an exception would be more useful, when the given topology does not exist... instead I'm getting a single row composed by nulls, or some other non-exception result

Change History (3)

comment:1 Changed 5 months ago by Sandro Santilli <strk@…>

In 74a85a0a/git:

Fix missing user errors from GetRingEdges?

References #4929 in main branch (3.2.0dev)

comment:2 Changed 5 months ago by Sandro Santilli <strk@…>

In 32df100/git:

Fix missing user errors from GetRingEdges?

References #4929 in 3.1 branch (3.1.3dev)

comment:3 Changed 5 months ago by strk

Milestone: PostGIS 3.2.0PostGIS 3.1.3
Resolution: fixed
Status: newclosed
Version: 2.5.x3.1.x

The bug was introduced in PostGIS-3.1.0, I fixed it in both main branch and stable 3.1, so will be fixed by PostGIS-3.1.3

Note: See TracTickets for help on using tickets.