From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Radek Strnad <radek(dot)strnad(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [WIP] collation support revisited (phase 1) |
Date: | 2008-07-11 07:29:18 |
Message-ID: | 20080711072918.GA11710@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jul 10, 2008 at 11:24:29PM +0200, Radek Strnad wrote:
> Hi,
>
> after long discussion with Mr. Kotala, we've decided to redesign our
> collation support proposal.
> For those of you who aren't familiar with my WIP patch and comments from
> other hackers here's the original mail:
> http://archives.postgresql.org/pgsql-hackers/2008-07/msg00019.php
<snip>
> phase 1
> Implement "sort of framework" so the PostgreSQL will have basic guts
> (pg_collation & pg_charset catalogs, CREATE COLLATION, add collation support
> for each type needed) and will support collation at database level. This
> phase has been accepted as a Google Summer of Code project.
Why bother with pg_charset? I don't think I've seen anyone even asking
for multiple charsets in a single DB and certainly no actual use case.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-07-11 07:34:34 | Re: Schema-qualified statements in pg_dump output |
Previous Message | Simon Riggs | 2008-07-11 07:03:40 | Re: [HACKERS] get_relation_stats_hook() |