Opened 4 years ago

Closed 8 months ago

#2809 closed defect (duplicate)

[raster] AddRasterConstraint does not check arguments upfront

Reported by: strk Owned by: Bborie Park
Priority: high Milestone: PostGIS 2.2.7
Component: raster Version: trunk
Keywords: Cc:


I was confused by AddRasterConstraint? failing with a vague message "could not add any constraint". Improving the error messages with r12722 I found out I had a typo in the column name, but still the AddRasterConstraint? function kept calling each constraint-specific method rather than immediately giving up.

It would be nicer if the existance of the target table/column and its readability would be checked upfront instead, giving a more human-readable message on failure.

Dunno how safe it would be to backport this (togheter with r12722) back till the 2.0 branch

Change History (7)

comment:1 Changed 4 years ago by Bborie Park

Priority: mediumhigh

comment:2 Changed 3 years ago by robe

Type: enhancementdefect

comment:3 Changed 3 years ago by robe

Milestone: PostGIS 2.2.0PostGIS 2.3.0

comment:4 Changed 3 years ago by robe

Milestone: PostGIS 2.3.0PostGIS 2.1.9

strk actually is this a 2.1 issue also I suspect so so switching this to 2.1.9. We can switch to 2.2.1 (after we relase 2.2.0) if it only affects 2.2+

comment:5 Changed 14 months ago by pramsey

Milestone: PostGIS 2.1.9PostGIS 2.2.6

comment:6 Changed 13 months ago by pramsey

Milestone: PostGIS 2.2.6PostGIS 2.2.7

comment:7 Changed 8 months ago by robe

Resolution: duplicate
Status: newclosed

Looks like already fixed in 2.2.7 and above.

Note: See TracTickets for help on using tickets.