Re: BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8
От | David Fetter |
---|---|
Тема | Re: BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8 |
Дата | |
Msg-id | 20061015225000.GC7037@fetter.org обсуждение исходный текст |
Ответ на | Re: BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8 (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8
|
Список | pgsql-bugs |
On Sun, Oct 15, 2006 at 06:12:43PM -0400, Tom Lane wrote: > David Fetter <david@fetter.org> writes: > > On Sun, Oct 15, 2006 at 04:43:17PM -0400, Tom Lane wrote: > >> ISTM the real question is what do we buy if we make such a > >> restriction? Getting rid of a few small ifdefs doesn't seem like > >> an adequate reason. Is there some major improvement we could > >> make? > > > UTF-8 handling much improved in 5.8. > > And? Sure there are good reasons why someone might want to use 5.8 > instead of 5.6, but how is that a reason for us to remove 5.6 > support? At some point, we will find something where we will have to duplicate some large hunk of 5.8's functionality to support 5.6. Why wait for that to happen? Murphy's Law says it will happen in a bug fix between two minor releases. Cheers, D -- David Fetter <david@fetter.org> http://fetter.org/ phone: +1 415 235 3778 AIM: dfetter666 Skype: davidfetter Remember to vote!
В списке pgsql-bugs по дате отправления: