Re: collation problem on 9.1-beta1

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Marc Cousin <cousinmarc(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: collation problem on 9.1-beta1
Date: 2011-06-02 12:09:45
Message-ID: 1307016585.2279.8.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On ons, 2011-05-11 at 14:58 -0400, Tom Lane wrote:
> Marc Cousin <cousinmarc(at)gmail(dot)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.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2011-06-02 14:10:04 Re: BUG #6047: prepare p1 as select 'now'::timestamp; then "execute p1" many times, they return the same time
Previous Message Artiom Makarov 2011-06-02 11:23:42 BUG #6048: TRUNCATE vs TRUNCATE CASCADE: misleading message