| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(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: Adding \x escape processing to COPY, psql, backend |
| Date: | 2005-05-30 19:41:19 |
| Message-ID: | 26407.1117482079@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Here is a new version of the three \x hex support patches. I have added
> \x for psql variables, which is the last patch.
> I have IM'ed with Peter and he is now OK with the idea of supporting \x,
> with the underestanding that it doesn't take us any farther away from
> compatibility than we are now.
Peter may be OK with it, but I object strongly to adding this to SQL
literals. This is exactly *not* the direction we want to be going in.
I don't really see the point for COPY and psql, either.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-05-30 20:11:08 | Backslash handling in strings |
| Previous Message | Bruce Momjian | 2005-05-30 19:33:38 | Adding \x escape processing to COPY, psql, backend |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-05-30 20:11:08 | Backslash handling in strings |
| Previous Message | Bruce Momjian | 2005-05-30 19:38:03 | Re: [ADMIN] Config option log_statement |