Re: Escape handling in COPY, strings, psql

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Sergey Ten <sergey(at)sourcelabs(dot)com>, "'Christopher Kings-Lynne'" <chriskl(at)familyhealth(dot)com(dot)au>, jason(at)sourcelabs(dot)com, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Escape handling in COPY, strings, psql
Date: 2005-05-29 11:36:54
Message-ID: 200505291336.55571.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce Momjian wrote:
> I thought about that, but adding additional escape letters isn't our
> problem --- it is the escape mechanism itself that is the issue.

In a random-encoding environment, the option to specify byte values
directly -- at any level -- is of limited value anyway and is a
potential source of errors. So let's stay away from that.

I did not find the original posts that your quotations came from, but it
has to be considered that COPY is also subject to encoding processing.
Overall, I find this proposal to be a dangerous option.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2005-05-29 13:30:06 Re: Escape handling in COPY, strings, psql
Previous Message Michael Paesold 2005-05-29 07:37:54 Re: [HACKERS] patches for items from TODO list

Browse pgsql-patches by date

  From Date Subject
Next Message Neil Conway 2005-05-29 13:27:33 skip FK trigger on UPDATE
Previous Message Michael Paesold 2005-05-29 07:37:54 Re: [HACKERS] patches for items from TODO list