Peter Headland wrote:
> In respect of Bruce's proposed changes, I prefer the original wording
> (for the same reasons as Tom), but with the addition of the mention of
> the server - "... read from or written to a file directly by the
> server".
OK, done with the attached patch.
--
Bruce Momjia
, 2010 22:01
To: Tom Lane
Cc: Peter Headland; Adrian Klaver; pgsql-general@postgresql.org
Subject: Re: [GENERAL] COPY command character set
Tom Lane wrote:
> Bruce Momjian writes:
> > I have updated the documentation to be more direct about COPY
encoding
> > behavior. Patch attached
Tom Lane wrote:
> Bruce Momjian writes:
> > I have updated the documentation to be more direct about COPY encoding
> > behavior. Patch attached and applied.
>
> Uh, why exactly do you find that better? "Processes data" seems a lot
> vaguer to me than the previous wording. I certainly don't thi
Bruce Momjian writes:
> I have updated the documentation to be more direct about COPY encoding
> behavior. Patch attached and applied.
Uh, why exactly do you find that better? "Processes data" seems a lot
vaguer to me than the previous wording. I certainly don't think that
this does much to ad
ber 10, 2009 11:06
> To: Peter Headland
> Cc: pgsql-general@postgresql.org; Tom Lane
> Subject: Re: [GENERAL] COPY command character set
>
>
> - "Peter Headland" wrote:
>
> > > The COPY command reference page saith
> > >
> > >I
Peter Headland wrote:
> As a general comment, I18N/L10N is a hairy enough topic that it merits
> its own heading in any commands where it is an issue.
I agree, this seems a good idea because people is often confused by
this.
--
Alvaro Herrerahttp://www.CommandPro
2009 11:06
To: Peter Headland
Cc: pgsql-general@postgresql.org; Tom Lane
Subject: Re: [GENERAL] COPY command character set
- "Peter Headland" wrote:
> > The COPY command reference page saith
> >
> >Input data is interpreted according to the current client
> e
ontributor...
--
Peter Headland
Architect
Actuate Corporation
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Thursday, September 10, 2009 11:13
To: Peter Headland
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] COPY command character set
"Peter Headla
"Peter Headland" writes:
> How about my suggestion to add a means (extend COPY syntax) to specify
> encoding explicitly and handle UTF lead bytes - would that be of
> interest?
There are no lead bytes in UTF-8, and we make no pretense of handling
UTF-16, so I don't think we'd be interested in som
- "Peter Headland" wrote:
> > The COPY command reference page saith
> >
> >Input data is interpreted according to the current client
> encoding,
> >and output data is encoded in the the current client encoding,
> even
> >if the data does not pass through the client but is read fr
yntax) to specify
encoding explicitly and handle UTF lead bytes - would that be of
interest?
--
Peter Headland
Architect
Actuate Corporation
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Thursday, September 10, 2009 10:38
To: Peter Headland
Cc: pgsql-general@postgresql
"Peter Headland" writes:
>> set client_encoding = 'utf8';
>> copy from stdin/to stdout;
> What if I want to do this on the server side (because it's much, much
> faster)? Does COPY use the default encoding of the database? If not,
> what?
> If this is a restrictive as it appears, and there are n
and
Architect
Actuate Corporation
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Wednesday, September 09, 2009 19:14
To: Peter Headland
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] COPY command character set
"Peter Headland" writes:
> The document
"Peter Headland" writes:
> The documentation of the COPY command does not state what character
> set(s) are recognized or written. I need to import and export UTF-8
> data; how can I do that?
set client_encoding = 'utf8';
copy from stdin/to stdout;
regards, tom lane
--
14 matches
Mail list logo
