| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Dynamic collation support |
| Date: | 2016-01-19 17:11:51 |
| Message-ID: | 8372.1453223511@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> On Tue, Jan 19, 2016 at 9:15 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> Different collates requires different plans - so using dynamic SQL is much
>> more correct.
>> It is same like using variables as columns or tablenames.
> Right -- I get it, and I understand the planner issues. But the
> amount of revision that goes into a database that internationalizes
> can be pretty large. To do it right, any static sql that involves
> string ordering can't be used. pl/sql also can't be used. ISTM this
> is impolite to certain coding styles.
Well, it's the way the SQL committee specified collations to work, so
we're pretty much stuck with that syntax.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kretschmer | 2016-01-19 17:13:59 | Re: How can i add a postgresql connection using inno setup? |
| Previous Message | Adrian Klaver | 2016-01-19 16:20:40 | Re: [GENERAL] about test_parser installation failure problem(PostgreSQL in 9.5.0)？ |