Gavin Sherry wrote:
> On Wed, 16 Oct 2002, Tom Lane wrote:
>
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > Right now we assume \XXX is octal. We could support \x as hex because
> > > \x isn't any special backslash character. However, no one has ever
> > > asked for this. Does anyone else
On Wed, 16 Oct 2002, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Right now we assume \XXX is octal. We could support \x as hex because
> > \x isn't any special backslash character. However, no one has ever
> > asked for this. Does anyone else think this would be benficial?
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Right now we assume \XXX is octal. We could support \x as hex because
> > \x isn't any special backslash character. However, no one has ever
> > asked for this. Does anyone else think this would be benficial?
>
> Well, it seems pr
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Right now we assume \XXX is octal. We could support \x as hex because
> \x isn't any special backslash character. However, no one has ever
> asked for this. Does anyone else think this would be benficial?
Well, it seems pretty localized and harmless.
Right now we assume \XXX is octal. We could support \x as hex because
\x isn't any special backslash character. However, no one has ever
asked for this. Does anyone else think this would be benficial?
---
Igor Georgiev w
1. Why i do
this:
I try to migrate a database with
a 200 tables from Sybase SQL Anywhere to PostgreSQL,
but SQL Anywhere escapes special
characters like a HEX values ( like \x0D \x2C . ).
PostgreSQL COPY FROM recognize
only OCT values ( lie \001 ... )
2. How-to it' easy :)))