Tom Lane wrote:
> > Third, I found out that psql has some unusual handling of escaped
> > numbers. Instead of using \ddd as octal, it has \ddd is decimal, \0ddd
> > is octal, and \0xddd is decimal. It is basically following the strtol()
> > rules for an escaped value. This seems confusing and co
Tom Lane wrote:
Bruce Momjian 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 thin
Bruce Momjian 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
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.
Third, I found out that psql has some unusual handling of escaped
numbers. Instead of
I have extracted the COPY \x part of your patch, and have attached it
for later application to CVS for 8.1.
---
Sergey Ten wrote:
> Hello all,
>
> Thank you to all who replied for suggestions and help. Enclosed please find
