[postgis-tickets] [PostGIS] #2359: raster2pgsql - large collection of examples of different bugs in -l (overviews)

[PostGIS]

#2359: raster2pgsql - large collection of examples of different bugs in -l
(overviews)
---------------------+------------------------------------------------------
  Reporter:  gbell   |       Owner:  dustymugs             
      Type:  defect  |      Status:  reopened              
  Priority:  medium  |   Milestone:  PostGIS 2.0.4         
 Component:  raster  |     Version:  2.0.x                 
Resolution:          |    Keywords:  raster2pgsql overviews
---------------------+------------------------------------------------------

Comment(by gbell):

 Hi dustymugs,

 I think this is becoming a difference of opinion about what defines a bug.

 In this case, raster2pgsql takes a role somewhat analogous to a software
 compiler, turning tiffs into SQL program output.

 The programs that are produced by r2pg generate *minimally helpful* error
 output when things go wrong - along with ugly and distracting error
 output. I think it's great when open source projects aim a bit higher than
 'minimally functional'.

 "The SQL generated by raster2pgsql IS valid."

 No, it is not. This is not the sort of thing someone should see when
 running valid SQL:

 invalid command \.
 ERROR:  syntax error at or near "01000001000000000000004E400000000000004"
 LINE 1: 01000001000000000000004E400000000000004EC00000000040E61A4100...

 I agree that there is an aspect of user error here. Nonetheless, that
 doesn't excuse sloppy error output to the user or random SQL bugs. Can you
 imagine if gcc was as unforgiving of user error and generated cryptic and
 unrelated extra messages around every real compiler warning?

 In this case, every PG Raster user must use this program to import their
 data, and many of those users will be unfamiliar with searching through
 junk output when things go wrong to find out what has happened.

 Perhaps we should move the suggestion to a dev mailing list for quick
 discussion/vote?

 Regarding my environment. It's a fedora 18 x86_64 base with manual builds
 of postgis, postgresql, gdal and geos.

 sl=# select postgis_full_version();

   postgis_full_version

 ----------------------------------------------------------------------------------------
 ----------------------------------------------------------------------------------------
 -------------------------
  POSTGIS="2.0.3 r11128" GEOS="3.3.8-CAPI-1.7.8" PROJ="Rel. 4.8.0, 6 March
 2012" GDAL="GD
 AL 1.10.0, released 2013/04/24" LIBXML="2.9.0" TOPOLOGY (topology procs
 from "2.0.2 r107
 89" need upgrade) RASTER
 (1 row)

 Please let me know if you would like versions for any of the fedora rpms.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2359#comment:5>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.