[prev in list] [next in list] [prev in thread] [next in thread]
List: postgis-devel
Subject: Re: [postgis-devel] [PostGIS] #1830: pgsql2shp fix for "XInvalid endian flag value encountered" on P
From: "PostGIS" <trac () osgeo ! org>
Date: 2012-05-28 15:53:45
Message-ID: 058.e779412f8738ec510c73dda5684bfc41 () osgeo ! org
[Download RAW message or body]
#1830: pgsql2shp fix for "XInvalid endian flag value encountered" on PostgreSQL
9.2
----------------------------+-----------------------------------------------
Reporter: dfuhry2 | Owner: pramsey
Type: defect | Status: reopened
Priority: high | Milestone: PostGIS 2.0.1
Component: loader/dumper | Version: 2.0.x
Resolution: | Keywords:
----------------------------+-----------------------------------------------
Comment(by mcayland):
Actually on second thoughts, that will penalise people using a new version
of libpq against a new PostgreSQL server since the point of hex encoding
is that it noticeably reduces the traffic on the wire between client and
server compared to escape encoding :(
Perhaps a better approach would be to perform PQunescapeBytea() on a hex-
encoded string such as '\x4d' - if the client library supports hex
encoding you'll get back an 'M', otherwise something different? I haven't
tried this, but it might be worth an experiment.
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1830#comment:9>
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. \
_______________________________________________ postgis-devel mailing list
postgis-devel@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic