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 StrnadOn Wed, Jul 2, 2008 at 8:22 PM, Gregory Stark <
stark@enterprisedb.com> wrote:
"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.
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!