| From: | Steve Peterson <steve(at)zpfe(dot)com> |
|---|---|
| To: | Richard Huxton <dev(at)archonet(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #1819: COPY filename rejects Windows format path |
| Date: | 2005-08-12 02:05:34 |
| Message-ID: | 6.2.1.2.0.20050811205311.021e0f38@209.98.88.108 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
At 09:47 AM 8/11/2005, Richard Huxton wrote:
>Steve Peterson wrote:
>>Running COPY FROM on a Windows server; using a Windows-format fully
>>qualified path with backslashes results in the backslashes being interpreted
>>as escapes.
>
>Did you escape the backslashes: C:\\Windows\\Path ?
Nope. I used a standard Windows path, copied from the address field in
Windows explorer.
I see now on
http://www.postgresql.org/docs/8.0/interactive/sql-syntax.html#SQL-SYNTAX-CONSTANTS
(I know, RTFM) that it's documented that the SQL string literal is extended
to accept backslash as an escape, so this is a documented behavior. Can I
convert this bug into a docs bug -- to mention the escaping process
wherever a filename is specified in a SQL string constant?
S
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2005-08-12 02:06:52 | Re: Cascading updates run seperately |
| Previous Message | Allan Wang | 2005-08-12 01:17:57 | Cascading updates run seperately |