From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Insufficient description in collation mismatch error |
Date: | 2011-04-19 23:13:15 |
Message-ID: | BANLkTimpwWRd_nNJwDSp2Lm05D1QPcAT8g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On 19 April 2011 23:57, Thom Brown <thom(at)linux(dot)com> wrote:
> Hi,
>
> I tried applying a collation to a GROUP BY clause without applying the
> collation to the corresponding column in the SELECT clause.
>
> postgres=# SELECT things, count(*) FROM stuff GROUP BY things COLLATE "C";
> ERROR: column "stuff.things" must appear in the GROUP BY clause or be
> used in an aggregate function
> LINE 1: SELECT things, count(*) FROM stuff GROUP BY things COLLATE "...
>
> Firstly, does it even make sense for a GROUP BY clause to accept COLLATE?
>
> Even if it does, this error message doesn't explain the problem, being
> that the column with the necessary collation doesn't appear in the
> SELECT.
Erk, please ignore. Wrong list.
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2011-04-20 09:30:35 | Re: pgAdmin III commit: Install adminpack on user request in frmStatus |
Previous Message | Thom Brown | 2011-04-19 22:57:19 | Insufficient description in collation mismatch error |