| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: How to pass around collation information |
| Date: | 2010-06-03 15:46:20 |
| Message-ID: | AANLkTinHZav655HKt6DGnlQsyWw5N4CdTbtaXRtVuArJ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 3, 2010 at 3:43 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On ons, 2010-06-02 at 16:56 -0400, Robert Haas wrote:
>> But in the end the only purpose of setting it on a column is to set
>> which one will be used for operations on that column. And the user
>> might still override it for a particular query.
>
> Of course. I'm just saying that it *can* be useful to attach a
> collation to a column definition, rather than only allowing it to be
> specified along with the sort operation.
Oh, I agree with that, for sure.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2010-06-03 15:53:09 | Re: functional call named notation clashes with SQL feature |
| Previous Message | Bruce Momjian | 2010-06-03 15:44:37 | Re: functional call named notation clashes with SQL feature |