[postgis-users] pgsql2shp changing case of fieldnames

[Obe, Regina DND\MIS]

The old one I had was dated sometime in 2003 and was compiled under cygwin,
but it still seemed to work when I upgraded to 8.0.  I think a -k switch
would be best.  

The older version preserved the case that was in postgres so for situations
where we needed UPPERCASE (standard shp behavior) we had to create views
that had the fields upper cased and dumped those out; so this new version
irradicates that need.  There are some situations where it is convenient to
keep the same case as postgres - e.g. it makes it easier to swap out a
postgis layer with a shape layer where postgis is not feasible for a
particular environment.  I'm assuming mapserver is still case sensitive with
field names in templates.

-----Original Message-----
From: strk at refractions.net [mailto:strk at refractions.net] 
Sent: Monday, May 09, 2005 11:26 AM
To: 'PostGIS Users Discussion'
Subject: Re: [postgis-users] pgsql2shp changing case of fieldnames


On Mon, May 09, 2005 at 10:18:52AM -0400, Obe, Regina     DNDMIS wrote:
> I noticed the 3/31/05 build of pgsql2shp I have now automatically 
> forces the output field names to upper case which normally would be a 
> good thing. Unfortunately I've got some old mapserver maps that rely 
> on the field names in the dbf being in lowercase.  Is there anyway to 
> reverse this behavior e.g. with a switch or something of that sort so 
> that I don't have to revert back to the older version of pgsql2shp?
>  
> Thanks,
> Regina

Which version of pgsql2shp doesn't do that ?
I guess we can revert the change back ... or add a -k switch
to it as well.

Does anyone see a problem with this ?

--strk;
_______________________________________________
postgis-users mailing list postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users