From: | Michael Paesold <mpaesold(at)gmx(dot)at> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Sergey Ten <sergey(at)sourcelabs(dot)com>, 'Christopher Kings-Lynne' <chriskl(at)familyhealth(dot)com(dot)au>, jason(at)sourcelabs(dot)com, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] patches for items from TODO list |
Date: | 2005-05-29 07:37:54 |
Message-ID: | 42997152.3090703@gmx.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>
>>Here is an updated version of the COPY \x patch. It is the first patch
>>attached.
>>Also, I realized that if we support \x in COPY, we should also support
>>\x in strings to the backend. This is the second patch.
>
>
> Do we really want to do any of these things? We've been getting beaten
> up recently about the fact that we have non-SQL-spec string escapes
> (ie, all the backslash stuff) so I'm a bit dubious about adding more,
> especially when there's little if any demand for it.
>
> I don't object too much to the COPY addition, since that's outside any
> spec anyway, but I do think we ought to think twice about adding this
> to SQL literal handling.
+1 from me on this for Tom -- please don't break spec compliance!
Best Regards,
Michael Paesold
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2005-05-29 11:36:54 | Re: Escape handling in COPY, strings, psql |
Previous Message | Oleg Bartunov | 2005-05-29 06:26:09 | Re: Bloom Filter indexes? |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2005-05-29 11:36:54 | Re: Escape handling in COPY, strings, psql |
Previous Message | Bruce Momjian | 2005-05-29 03:58:01 | Escape handling in COPY, strings, psql |