| From: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
|---|---|
| To: | |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gregory Stark <stark(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Radek Strnad <radek(dot)strnad(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [WIP] patch - Collation at database level |
| Date: | 2008-07-08 09:27:35 |
| Message-ID: | 48733307.10200@sun.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zdenek Kotala napsal(a):
>
> I though more about it and I discussed it with Radek yesterday. The
> problem is that collation must be created before user want to use CREATE
> DATABASE ... COLLATE ... command. It inclines to have have pg_collation
> as a global catalog, but ANSI specifies to use schema name in collation
> specification and schemes are database specific ... It means that
> pg_collation have to be non-shared catalog and new database only
> inherits collation from template db. And CREATE DATABASE have to check
> list of collation in template database :(.
thinking more ...
It must be shared catalog because pg_database will depend on it.
Zdenek
--
Zdenek Kotala Sun Microsystems
Prague, Czech Republic http://sun.com/postgresql
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2008-07-08 09:49:52 | Re: [WIP] patch - Collation at database level |
| Previous Message | Simon Riggs | 2008-07-08 09:21:13 | Re: [patch] plproxy v2 |