[QGIS-trac] Re: [Quantum GIS] #2189: Map Server Export - POSTGIS data

[Quantum GIS]

#2189: Map Server Export - POSTGIS data
-----------------------------------------------------+----------------------
        Reporter:  smccabe33                         |         Owner:  rduivenvoorde
            Type:  bug                               |        Status:  assigned     
        Priority:  major: does not work as expected  |     Milestone:  Version 1.4.0
       Component:  Python plugins and bindings       |       Version:  HEAD         
      Resolution:                                    |      Keywords:               
Platform_version:                                    |      Platform:  Debian       
        Must_fix:  No                                |   Status_info:  1            
-----------------------------------------------------+----------------------
Changes (by jef):

  * component:  Build/Install => Python plugins and bindings

Comment:

 Replying to [comment:6 rduivenvoorde]:
 > the plugin does already do this (adding "using unique ...") via some
 guessing based on column names...

 Does it also add srid?   mapserver might detect that it doesn't need to
 parse the SQL statement to get table and column name to query
 geometry_columns, if both are there.  And that parsing might be the origin
 of the problem.

 speaking of which: r12369 the key field is in all postgres layers - not
 only views like before.

 > So my guess is that the column names or tablenames of smccabe33 were
 non-lowercase, so after adding the quotes those names did not match any
 more (while when removing the quotes: postgresql are always "folded to
 lowercase" it was ok).

 That shouldn't matter.  If the column name was indeed uppercase, QGIS
 would have reported it uppercase - and I guess you would have quoted it
 just like that.

 The postgres provider even works with column names like {{{This is a
 ridiculously non-trivial}}}[[br]]
 {{{"column name", isn't it?}}} (ie. mixed case identifier with blanks,
 quotes, a question mark and even a newline.  Not sure about mapserver.

 > Bringing it back to the question (I think): "should or should we not put
 quotes around column and table names in DATA and FILTER rulse" in the
 mapfile.

 I think we must quote identifiers - that also what the postgres provider
 does.

-- 
Ticket URL: <https://trac.osgeo.org/qgis/ticket/2189#comment:8>
Quantum GIS <http://qgis.org>
Quantum GIS is an Open Source GIS viewer/editor supporting OGR, PostGIS, and GRASS formats