Re: [WIP] patch - Collation at database level - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: [WIP] patch - Collation at database level
Date
Msg-id 871w2ccfjh.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: [WIP] patch - Collation at database level  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [WIP] patch - Collation at database level  (Martijn van Oosterhout <kleptog@svana.org>)
Re: [WIP] patch - Collation at database level  ("Radek Strnad" <radek.strnad@gmail.com>)
Re: [WIP] patch - Collation at database level  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> Alvaro Herrera <alvherre@commandprompt.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!


pgsql-hackers by date:

Previous
From: Teodor Sigaev
Date:
Subject: Re: [PATCHES] GIN improvements
Next
From: Martijn van Oosterhout
Date:
Subject: Re: [WIP] patch - Collation at database level