| From: | Mario Weilguni <mweilguni(at)sime(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Albe Laurenz <all(at)adv(dot)magwien(dot)gv(dot)at>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Bug in UTF8-Validation Code? |
| Date: | 2007-03-13 15:42:35 |
| Message-ID: | 200703131642.36079.mweilguni@sime.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Am Dienstag, 13. März 2007 16:38 schrieb Joshua D. Drake:
> Andrew Dunstan wrote:
> > Albe Laurenz wrote:
> >> A fix could be either that the server checks escape sequences for
> >> validity
> >
> > This strikes me as essential. If the db has a certain encoding ISTM we
> > are promising that all the text data is valid for that encoding.
> >
> > The question in my mind is how we help people to recover from the fact
> > that we haven't done that.
>
> Is this any different than the issues of moving 8.0.x to 8.1 UTF8? Where
> we had to use iconv?
>
What issues? I've upgraded several 8.0 database to 8.1. without having to use
iconv. Did I miss something?
Regards,
Mario Weilguni
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-03-13 15:45:17 | Re: Major Feature Interactions |
| Previous Message | Joshua D. Drake | 2007-03-13 15:38:01 | Re: Bug in UTF8-Validation Code? |