From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: \copy command: how to define a tab character as the delimiter |
Date: | 2010-03-09 18:41:26 |
Message-ID: | 4B969656.4090005@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 03/09/2010 10:09 AM, Thomas Kellerer wrote:
> Raymond O'Donnell wrote on 09.03.2010 18:39:
>> This is Postgres you're talking about - of course it's that easy! :-)
>
> :)
>
> The main reason I asked, was that the manual actually claims that '\t'
> can be used ("The following special backslash sequences are recognized
> by COPY FROM")
>
> As this is part of the description for the COPY command, does this maybe
> mean it is only valid for COPY but not for \copy?
> if that is the case, it should be documented somewhere).
>
> Or is this related to the value of standard_conforming_strings?
>
> Thomas
>
>
From here:
http://www.postgresql.org/docs/8.4/interactive/app-psql.html
"The syntax of the command is similar to that of the SQL COPY command.
Note that, because of this, special parsing rules apply to the \copy
command. In particular, the variable substitution rules and backslash
escapes do not apply. "
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2010-03-09 19:31:07 | Re: Not all functions in schema pg_catalog are "visible" |
Previous Message | Dan Fitzpatrick | 2010-03-09 18:35:23 | Re: Update view/table rule order of operations or race condition |