| From: | Mark Roberts <mailing_lists(at)pandapocket(dot)com> |
|---|---|
| To: | Marco Colombo <pgsql(at)esiway(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Good Delimiter for copy command |
| Date: | 2009-02-17 17:47:15 |
| Message-ID: | 1234892835.11148.295.camel@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Tue, 2009-02-17 at 17:17 +0100, Marco Colombo wrote:
>
> Which makes me wonder, does copy accept UTF-8 input? Is it possibile
> to use some unicode character which is unlikely to appear in the data
> set as delimiter? Something like U+FFFC.
I'm also not able to get unicode characters to copy in like that, but I
also haven't had any problems with data containing the *tab* character.
It seems to be properly escaped (see my other email in this thread) so
it doesn't seem to matter if it appears in the data stream. The *only*
reason I see to switch from tab is if the receiving application requires
it in a different format.
-Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2009-02-17 17:53:00 | Re: hi all |
| Previous Message | Dave Page | 2009-02-17 17:37:03 | Re: [GENERAL] 8.3 doc issue |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2009-02-17 17:55:02 | Re: Good Delimiter for copy command |
| Previous Message | Bruce Momjian | 2009-02-17 16:58:11 | vacuumdb --freeze |