Ticket #594 (closed task: fixed)

Opened 3 years ago

Last modified 7 months ago

[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

  Changed 3 years ago by pracine

  • status changed from new to assigned

  Changed 2 years ago by pracine

  • owner changed from pracine to jorgearevalo
  • status changed from assigned to new

  Changed 2 years ago by jorgearevalo

  • status changed from new to assigned

  Changed 16 months ago by pracine

  • milestone changed from PostGIS 2.0.0 to PostGIS Raster 2.0.1

  Changed 15 months ago by pracine

  • milestone changed from PostGIS Raster 2.0.1 to PostGIS 2.0.1

  Changed 13 months ago by pramsey

  • milestone changed from PostGIS 2.0.1 to PostGIS 2.1.0

  Changed 7 months 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.

follow-up: ↓ 9   Changed 7 months ago by dustymugs

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

Resolved as of r10586 with audit.

in reply to: ↑ 8   Changed 7 months 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?

  Changed 7 months 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.