Re: Dynamic collation support

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Dynamic collation support
Date: 2016-01-19 15:15:11
Message-ID: CAFj8pRCbS=zrgkvT9xfrSehOnt3p7zHbjOZ02pL8UF8fZMmPXQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2016-01-19 16:07 GMT+01:00 Merlin Moncure <mmoncure(at)gmail(dot)com>:

> For database functions, is there any way to manage collations besides
> dynamic sql? It doesn't look like there is but I thought I'd ask.
>
> For example, I want to do something like:
>
> DO
> $$
> DECLARE
> c name DEFAULT 'en_GB';
> BEGIN
> SELECT * FROM foo ORDER BY a COLLATE c;
> END;
> $$;
>
> and not
>
> DO
> $$
> DECLARE
> c name DEFAULT 'en_GB';
> BEGIN
> EXECUTE 'SELECT * FROM foo ORDER BY a COLLATE ' || quote_ident(c);
> END;
> $$;
>
> I understand this would disable all index supported sorting; that's ok.
>
> Not being able to specify collation in a parameterized manner presents
> some issues...I'm curious if there are workarounds.
>

Different collates requires different plans - so using dynamic SQL is much
more correct.

It is same like using variables as columns or tablenames.

Regards

Pavel

>
> merlin
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2016-01-19 15:42:36 Re: Dynamic collation support
Previous Message Merlin Moncure 2016-01-19 15:07:29 Dynamic collation support