| From: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: COPY fails on 8.1 with invalid byte sequences in text |
| Date: | 2006-11-03 18:29:57 |
| Message-ID: | 454B8AA5.60608@zigo.dhs.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Tom Lane skrev:
>> Is this not a bug?
>
> I don't actually see that it is. The documentation is perfectly clear
> on the point:
>
> (It is your responsibility that the byte sequences you create
> are valid characters in the server character set encoding.)
>
> (This is in 4.1.2.1. String Constants) If you don't want to deal with
> this, don't use octal escapes to construct multibyte characters.
The database also has a responsibility to protect itself. If you can
insert data into the database so that the stored value is invalid for
the datatype of the column, then it's broken imho.
Having a statement in the doc saying "please don't do this because you
will corrupt the data" doesn't really make the situation better.
/Dennis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2006-11-03 20:25:22 | Re: COPY fails on 8.1 with invalid byte sequences in text |
| Previous Message | Tom Lane | 2006-11-03 16:12:15 | Re: 8.2bet2 failed build on Solaris 10 / x86-64 / SUN Studio |