Opened 15 years ago

Last modified 15 years ago

#104 closed defect

shp2pgsql is using deprecated PostgreSQL escape syntax — at Version 4

Reported by: robe Owned by: robe
Priority: low Milestone:
Component: postgis Version:
Keywords: Cc:

Description (last modified by robe)

For some datasets I get this

HINT: Use the escape string syntax for backslashes, e.g., E'
'. WARNING: nonstandard use of
in a string literal LINE 1: …w','St','Brighton','02135','Residential','3','R3','\\2003\\2...

Change History (6)

comment:1 by pramsey, 15 years ago

Try this micro-patch and see if it goes away…

comment:2 by robe, 15 years ago

That seems to work. You going to commit?

by robe....@…, 15 years ago

Attachment: esc.patch​ added

​http://postgis.googlecode.com/issues/attachment?aid=-5423139989644836315&name=esc.patch

comment:3 by pramsey, 15 years ago

Committed at r3623

by robe, 15 years ago

Attachment: Aban01.zip​ added

sample file

comment:4 by robe, 15 years ago

Description: modified (diff)
Resolution: fixed
Status: closed → reopened

I think the changes done in #123 r3989 broke this and worst yet, I can no longer import my sample file with either shp2pgsql or the shp2pgsql gui. Gives the annoying escape errors and also that I have invalid characters for SQL ASCII or some such thing. The -W latin1 also doesn't work.

Try attached file.

Note: See TracTickets for help on using tickets.