just try the SQL definition of your map file in a normal query client like Pgadmin (dropping the parts starting with "USING..."). It will probably not work either... I would strongly recommend to *not* use upper case characters in Postgres columns unless you really know how to handle them, and how they are handled by Mapserver.
armin On 25/02/2010 16:05, giorgio61 wrote: > > hello i am experiencing a very strange behaviour in a p.mapper mapfile > i hope i can explain it properly > i have a postgis layer defintiion that was not working. I spent many hours > changing it in order to realize where is the problem also because the simple > defintion > > DATA "the_geom from (select * from srd_comuni) as foo USING UNIQUE gid USING > srid=3003" > > is working perfectly. things didnt go well when i wanted to list the fields > to select inspite of the * and i also wanted to create a JOIN. > For example this query doesnt work > > DATA "the_geom FROM (SELECT srd_comuni.gid as gid, srd_comuni.the_geom as > the_geom, srd_comuni.A09010103 FROM srd_comuni) AS foo USING SRID=3003 USING > UNIQUE gid" > > try and try i realized that the problem was in the field named A09010103. > try and try i realized that if i changed the name of the field the quesry > worked. it could be named province_code or also a09010103 but not A09010103 > and not even A090 or B090. This is a mystery for me. Any help? > > > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ pmapper-users mailing list pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users
