| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: invalidly encoded strings |
| Date: | 2007-09-10 03:52:33 |
| Message-ID: | 1189396353.5924.35.camel@jdavis |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Sun, 2007-09-09 at 23:33 -0400, Andrew Dunstan wrote:
> Tom Lane wrote:
> > In the short run it might be best to do it in scan.l after all.
> >
>
> I have not come up with a way of doing that and handling the bytea case.
> If you have I'm all ears. And then I am still worried about COPY.
If it's done in the scanner it should still accept things like:
E'\\377\\000\\377'::bytea
right?
I think the concern is when they use only one slash, like:
E'\377\000\377'::bytea
which, as I mentioned before, is not correct anyway.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-09-10 04:03:06 | Re: invalidly encoded strings |
| Previous Message | Tom Lane | 2007-09-10 03:43:48 | Re: invalidly encoded strings |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-09-10 04:03:06 | Re: invalidly encoded strings |
| Previous Message | Tom Lane | 2007-09-10 03:43:48 | Re: invalidly encoded strings |