Opened 7 years ago

Closed 4 years ago

Last modified 4 years ago

#594 closed task (fixed)

[raster] Better handling for NULL, ST_IsEmpty, ST_HasNoBand and ST_BandIsNodata rasters

Reported by: pracine Owned by: jorgearevalo
Priority: medium Milestone: PostGIS 2.1.0
Component: raster Version: trunk
Keywords: Cc:

Description

Every functions should better handle those four possibilities.

Change History (10)

comment:1 Changed 7 years ago by pracine

Status: newassigned

comment:2 Changed 6 years ago by pracine

Owner: changed from pracine to jorgearevalo
Status: assignednew

comment:3 Changed 6 years ago by jorgearevalo

Status: newassigned

comment:4 Changed 5 years ago by pracine

Milestone: PostGIS 2.0.0PostGIS Raster 2.0.1

comment:5 Changed 5 years ago by pracine

Milestone: PostGIS Raster 2.0.1PostGIS 2.0.1

comment:6 Changed 5 years ago by pramsey

Milestone: PostGIS 2.0.1PostGIS 2.1.0

comment:7 Changed 4 years ago by dustymugs

This ticket is vague. Better handling where? At the SQL level? In C? In C, all of these elements are accounted for. I'll do a quick audit of the SQL code and then close this ticket.

Future tickets really need to be more specific with examples if possible.

comment:8 Changed 4 years ago by dustymugs

Resolution: fixed
Status: assignedclosed

Resolved as of r10586 with audit.

comment:9 in reply to:  8 Changed 4 years ago by pracine

Replying to dustymugs:

Resolved as of r10586 with audit.

Hum, is it possible that this last comment was not intended to this ticket?

comment:10 Changed 4 years ago by dustymugs

The comment is correct. As part of the audit, I ended up fixing other stuff.

Note: See TracTickets for help on using tickets.