From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Marc Cousin <cousinmarc(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: collation problem on 9.1-beta1 |
Date: | 2011-05-11 18:58:57 |
Message-ID: | 4542.1305140337@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-05-11 19:39:05 | Re: [GENERAL] postgresql-8.4 error -> BUG |
Previous Message | Magnus Hagander | 2011-05-11 18:57:09 | Re: Changed behaviour of \' |