Re: collation problem on 9.1-beta1

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marc Cousin <cousinmarc(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: collation problem on 9.1-beta1
Date: 2011-06-09 17:30:41
Message-ID: 201106091730.p59HUfB08649@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Peter Eisentraut wrote:
> 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.

Column numbers in ORDER BY is ANSI syntax so I don't think calling them
"legacy" is accurate. "limited functionality"?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2011-06-09 18:19:29 Re: collation problem on 9.1-beta1
Previous Message Peter Eisentraut 2011-06-09 15:00:30 Re: BUG #5926: information schema dtd_identifier for element_types, columns, parameters views inconsistent