[postgis-tickets] [PostGIS] #3147: [raster] raster2pgsql should check that the resulting table name it's a valid SQL name.

[PostGIS]

#3147: [raster] raster2pgsql should check that the resulting table name it's a
valid SQL name.
-------------------------+---------------------------
  Reporter:  tinproject  |      Owner:  dustymugs
      Type:  defect      |     Status:  new
  Priority:  low         |  Milestone:  PostGIS 2.1.8
 Component:  raster      |    Version:  2.1.x
Resolution:              |   Keywords:  raster2pgsql
-------------------------+---------------------------

Comment (by robe):

 tinproject,

 is this error being generated from within raster2pgsql, or just when you
 manually run those statements.

 Normally you pass the table name into raster2pgsql for what you want the
 new table.

 and

 if you didn't you should be doing:


 {{{
 SELECT * FROM "0457j30";
 }}}

 since there is nothing technically wrong with a table name 0457j30.

 For things like that, not sure I agree that raster2pgsql should try to
 come up with a name that doesn't require quoting by default. Perhaps as an
 additional switch option, but I would expect some people might rely on the
 current behavior, so defintely  not something we can put in a micro unless
 it's actually breaking now in raster2.pgsql.

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3147#comment:1>
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.