Opened 14 years ago

Closed 12 years ago

Last modified 12 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: master
Keywords: Cc:

Description

Every functions should better handle those four possibilities.

Change History (10)

comment:1 by pracine, 14 years ago

Status: new → assigned

comment:2 by pracine, 14 years ago

Owner: changed from pracine to jorgearevalo
Status: assigned → new

comment:3 by jorgearevalo, 14 years ago

Status: new → assigned

comment:4 by pracine, 13 years ago

Milestone: PostGIS 2.0.0 → PostGIS Raster 2.0.1

comment:5 by pracine, 13 years ago

Milestone: PostGIS Raster 2.0.1 → PostGIS 2.0.1

comment:6 by pramsey, 13 years ago

Milestone: PostGIS 2.0.1 → PostGIS 2.1.0

comment:7 by dustymugs, 12 years ago

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 by dustymugs, 12 years ago

Resolution: → fixed
Status: assigned → closed

Resolved as of r10586 with audit.

in reply to:  8 comment:9 by pracine, 12 years ago

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 by dustymugs, 12 years ago

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

Note: See TracTickets for help on using tickets.