Re: FW: [postgis-users] ": can't parse "ne 1, pg_atoi: error in " &empty strings in shp2pgsql output...
От | Jason Tishler |
---|---|
Тема | Re: FW: [postgis-users] ": can't parse "ne 1, pg_atoi: error in " &empty strings in shp2pgsql output... |
Дата | |
Msg-id | 20030915132807.GI1840@tishler.net обсуждение исходный текст |
Ответ на | FW: [postgis-users] ": can't parse "ne 1, pg_atoi: error in " &empty strings in shp2pgsql output... (Mike Leahy <mgleahy@fes.uwaterloo.ca>) |
Список | pgsql-cygwin |
Mike, On Sun, Sep 14, 2003 at 12:19:52PM -0400, Mike Leahy wrote: > On Norman's recommendation below, I'm forwarding this question to this > list... > > -----Original Message----- > From: postgis-users-bounces@postgis.refractions.net > [mailto:postgis-users- bounces@postgis.refractions.net] On Behalf Of > Norman Vine > Sent: September 13, 2003 8:48 PM > To: PostGIS Users Discussion > Subject: RE: [postgis-users] ": can't parse "ne 1, pg_atoi: error in " > &empty strings in shp2pgsql output... > > Mike Leahy writes: > > I've just installed Cygwin (on WinXP) and compiled the latest > > available versions of PostgreSQL/PostGIS. > > > > When I run a COPY query to import data from a tab-separated DOS-text > > file I get the following message: > > > > ": can't parse "ne 1, pg_atoi: error in " > > > > [snip] > > I've tried compiling PostgreSQL/PostGIS with all the fopen or popen > > commands with the t argument for text). The above is the right approach, but it sounds like you are still opening the files in binary mode. Additionally, you may want to restrict just opening COPY files in text mode (if possible) to avoid breaking other areas. If you figure out how to fix this issue, then please submit a patch to pgsql-patches@. Thanks, Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
В списке pgsql-cygwin по дате отправления: