Dave Fuhry wrote:
I use the attached patch, which tweaks shp2pgsql to handle newlines
(\n) and carriage returns (\r), replaces hi-bit characters with a
question mark, and removes some geometry checks.
You probably only want to do the first of those three. In that case,
the patch should be easy to modify. Hope you find it helpful.
-Dave
Yeah, the escaping part was a bug in shp2pgsql - the rules for escaping
COPY sequences were wrong. I've just applied a modified escaping patch
to SVN which removes the E'...' notation and now uses the correct
escaping for both COPY and INSERT modes.
ATB,
Mark.
--
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
