[Bug] COPY staments with paths containing non-ASCII characters under WinXP
От | Joachim Raue |
---|---|
Тема | [Bug] COPY staments with paths containing non-ASCII characters under WinXP |
Дата | |
Msg-id | 012d01ca83ef$3f075cf0$bd1616d0$@net обсуждение исходный текст |
Список | pgsql-bugs |
Hi, =20 I observed following bug in Postgres 8.4 under Windows XP with German locale: =20 - I create a text file C:\Foo\F=F6=F6.txt with valid one column CSV content, let it be =93a=94 in quotes - In PgAdmin 1.10.0, I then run: CREATE DATABASE test ENCODING =3D 'UTF8' LC_COLLATE =3D 'German_Germany.1252' LC_CTYPE =3D 'German_Germany.1252' CONNECTION LIMIT =3D -1; =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 create table bar ( foobar text ); =20 COPY bar FROM E'C:\\Foo\\F=F6=F6.txt' WITH CSV =20 - The COPY statement will fail if the path contains special characters. Renaming F=F6=F6 into Foo would work. Message returned in German locale: =20 FEHLER: konnte Datei =BBC:\Foo\F=F6=F6.txt=AB nicht zum Lesen =F6ffnen: No= such file or directory =20 ********** Fehler ********** =20 FEHLER: konnte Datei =BBC:\Foo\F=F6=F6.txt=AB nicht zum Lesen =F6ffnen: No = such file or directory SQL Status:58P01 =20 Your advice on worksarounds is appreciated. My guess is that the problem is the file name being given in UTF8 (DB default), but Windows paths being stored in an 1-bye encoding. =20 Best wishes and seasonal greetings, =20 Joachim =20 =20
В списке pgsql-bugs по дате отправления: