Re: Bug in UTF8-Validation Code?
От | Joshua D. Drake |
---|---|
Тема | Re: Bug in UTF8-Validation Code? |
Дата | |
Msg-id | 45F6C559.7060909@commandprompt.com обсуждение исходный текст |
Ответ на | Re: Bug in UTF8-Validation Code? (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: Bug in UTF8-Validation Code?
|
Список | pgsql-hackers |
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? Joshua D. Drake > > cheers > > andrew > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings > -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/
В списке pgsql-hackers по дате отправления: