Re: collation problem on 9.1-beta1

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: collation problem on 9.1-beta1
Дата
Msg-id 1307016585.2279.8.camel@vanquo.pezone.net
обсуждение исходный текст
Ответ на Re: collation problem on 9.1-beta1  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: collation problem on 9.1-beta1  (Marc Cousin <cousinmarc@gmail.com>)
Re: collation problem on 9.1-beta1  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-bugs
On ons, 2011-05-11 at 14:58 -0400, Tom Lane wrote:
> Marc Cousin <cousinmarc@gmail.com> writes:
> > I've been starting to work on a 'what's new in 9.1' like i did last
> > year, and am faced with what I feel is a bug, while building a demo case
> > for collation.
>
> > Here it is:
>
> > SELECT * from (values ('llegar'),('llorer'),('lugar')) as tmp
> > order by 1 collate "es_ES.utf8";
> > ERROR:  collations are not supported by type integer at character 74
>
> This isn't a bug, or at least not one we're going to fix.  ORDER BY
> column-number is a legacy syntax that doesn't support many options, and
> COLLATE is one of the ones that it doesn't support.
>
> (The actual technical reason for this is that COLLATE turns the argument
> into a general expression, not something we can special-case.  You would
> get the same error from writing "1 COLLATE something" anyplace else.)

Well, I'm just counting how many more people are going to complain about
this before fixing it.  Possibly in 9.2.

В списке pgsql-bugs по дате отправления:

Предыдущее
От: "Artiom Makarov"
Дата:
Сообщение: BUG #6048: TRUNCATE vs TRUNCATE CASCADE: misleading message
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #6047: prepare p1 as select 'now'::timestamp; then "execute p1" many times, they return the same time