Avoid use of bogus AddRasterConstraint when running upgrade tests

Works around bug #4547

Closes #4530

git-svn-id: http://svn.osgeo.org/postgis/trunk@17920 b70326c6-7e19-0410-871a-916f4a2858ee

diff --git a/regress/run_test.pl b/regress/run_test.pl
index bbc5f63ffa56c0803d9abf52a6a558c567f34129..1a845c982ef4241f27b6ddf8e052466313b43e3a 100755 (executable)
--- a/regress/run_test.pl
+++ b/regress/run_test.pl
@@ -320,12 +320,12 @@ sub create_upgrade_test_objects
 
   if ( $OPT_WITH_RASTER )
   {
-    $query = "insert into upgrade_test(r) ";
-    $query .= "select ST_AddBand(ST_MakeEmptyRaster(10, 10, 1, 1, 2, 2, 0, 0,4326), 1, '8BSI'::text, -129, NULL);";
+    $query = "UPDATE upgrade_test SET r = ";
+    $query .= " ST_AddBand(ST_MakeEmptyRaster(10, 10, 1, 1, 2, 2, 0, 0,4326), 1, '8BSI'::text, -129, NULL);";
     $ret = sql($query);
-    unless ( $ret =~ /^INSERT/ ) {
+    unless ( $ret =~ /^UPDATE/ ) {
       `dropdb $DB`;
-      print "\nSomething went wrong inserting raster into upgrade_test table: $ret.\n";
+      print "\nSomething went wrong setting raster into upgrade_test table: $ret.\n";
       exit(1);
     }