From: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> |
---|---|
To: | Mahmoud Taghizadeh <m_taghi(at)yahoo(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: NLS support for postgreSQL |
Date: | 2004-08-22 12:40:25 |
Message-ID: | Pine.LNX.4.44.0408221430310.9559-100000@zigo.dhs.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, 22 Aug 2004, Mahmoud Taghizadeh wrote:
> 3. we are planning to add locale per column for
> postgreSQL, but I found that you had said its
> impossible. am I right? do you have any paper about
> it?
>
> 4. If I want to add collate order for postgreSQL what
> should I do? is there any guideline for adding this
> feature in postgreSQL
Impossible is way to strong word. It's just a lot of work.
Encoding and collation order should be per column (is there any more local
information needed then collation order?). In fact, each string handled
inside pg need such information stored. It's similar to a type of an
object, and can probably be handled in a similar way.
What I suggest is that you first check out the sql specification (already
sql92 includes this) and whatever solution made should support what's in
the standard (or at least be as close as possible). We don't just want to
code up something that works somewhat and that later makes it hard to do
the right thing demanded by the standard. I'm not saying that one have to
do everything that's in the standard, just that what we do should not
break the standard in arbitrary ways.
--
/Dennis Björklund
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-22 16:52:18 | Re: pg_hba.conf and IP-MASK |
Previous Message | Peter Eisentraut | 2004-08-22 12:31:36 | Re: NLS support for postgreSQL |