From: | "Radek Strnad" <radek(dot)strnad(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [WIP] patch - Collation at database level |
Date: | 2008-07-02 19:21:06 |
Message-ID: | de5165440807021221s26b1feaam461319aa1fe94ed2@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
My patch should be "sort of" wrapper that will implement guts for further
development (collation at column level) like catalogs, creating collations
etc. When creating collation user will be able to choose which function to
use (by statement STRCOLFN - not in SQL standard). In the first stage I'll
implement function that will use system locales. Adding ICU or any other
library won't be that big deal.
Radek Strnad
On Wed, Jul 2, 2008 at 8:22 PM, Gregory Stark <stark(at)enterprisedb(dot)com>
wrote:
> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>
> > Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> >> Why does a collation have a schema?
> >
> > Because the SQL spec says so. Also, if we don't put them in schemas,
> > we have no nice way to distinguish built-in and user-defined collations,
> > which creates a problem for pg_dump.
>
> Out of curiosity, what is a "user-defined collation"? Are there SQL
> statements
> to go around declaring what order code points should be sorted in? That
> seems
> like it would be... quite tedious!
>
> --
> Gregory Stark
> EnterpriseDB http://www.enterprisedb.com
> Ask me about EnterpriseDB's Slony Replication support!
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ken Camann | 2008-07-02 19:32:43 | Re: A Windows x64 port of PostgreSQL |
Previous Message | Teodor Sigaev | 2008-07-02 19:18:49 | Re: PATCH: CITEXT 2.0 |