From 6426a437798eb0d080462472940840dcdda6dee1 Mon Sep 17 00:00:00 2001 From: Bborie Park Date: Sat, 7 Jan 2012 00:42:18 +0000 Subject: [PATCH] Fixed handling of NODATA value constraint as band with no NODATA was being constrained with the value of zero. git-svn-id: http://svn.osgeo.org/postgis/trunk@8691 b70326c6-7e19-0410-871a-916f4a2858ee --- raster/rt_pg/rtpostgis.sql.in.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/raster/rt_pg/rtpostgis.sql.in.c b/raster/rt_pg/rtpostgis.sql.in.c index 039fe3de7..4f2774a60 100644 --- a/raster/rt_pg/rtpostgis.sql.in.c +++ b/raster/rt_pg/rtpostgis.sql.in.c @@ -4141,7 +4141,7 @@ CREATE OR REPLACE FUNCTION _raster_constraint_info_nodata_values(rastschema name CREATE OR REPLACE FUNCTION _raster_constraint_nodata_values(rast raster) RETURNS double precision[] AS - $$ SELECT array_agg(nodatavalue)::double precision[] FROM st_bandmetadata($1, ARRAY[]::int[]); $$ + $$ SELECT array_agg(CASE WHEN hasnodata IS TRUE THEN nodatavalue ELSE NULL END)::double precision[] FROM st_bandmetadata($1, ARRAY[]::int[]); $$ LANGUAGE 'sql' STABLE STRICT; CREATE OR REPLACE FUNCTION _add_raster_constraint_nodata_values(rastschema name, rasttable name, rastcolumn name) -- 2.40.0