Re: [HACKERS] charset/collation in values

2004-11-02 Thread Tatsuo Ishii
> Dennis Bjorklund wrote: > > The named entity that is called a collation works for a character > > repertoire. It would need to handle different charsets for that > > repertoire of course. So there would be one collation called say > > ucs_sv and not utf8_sv, utf16_sv, utf32_sv. > > Again, theore

Re: [HACKERS] charset/collation in values

2004-11-02 Thread Peter Eisentraut
Dennis Bjorklund wrote: > The named entity that is called a collation works for a character > repertoire. It would need to handle different charsets for that > repertoire of course. So there would be one collation called say > ucs_sv and not utf8_sv, utf16_sv, utf32_sv. Again, theoretically, this

Re: [HACKERS] charset/collation in values

2004-11-02 Thread Dennis Bjorklund
On Tue, 2 Nov 2004, Peter Eisentraut wrote: > For the theoretical specification of a collation, it might suffice to > know the character repertoire. But I think in practice, the > implementation of a collation will require knowing the specific > character encoding. The named entity that is calle

Re: [HACKERS] charset/collation in values

2004-11-02 Thread Peter Eisentraut
Am Dienstag, 2. November 2004 13:53 schrieb Tatsuo Ishii: > In my understanding the relation between charset and collation is > 1:N. Thus storing only a collation is sufficient to determine the > charset. However a charset cannot determine a collation. Exactly. -- Peter Eisentraut http://develop

Re: [HACKERS] charset/collation in values

2004-11-02 Thread Peter Eisentraut
Am Dienstag, 2. November 2004 13:15 schrieb Dennis Bjorklund: > On Tue, 2 Nov 2004, Peter Eisentraut wrote: > > A collation implies a character set, so you only need to store one piece > > of information anyway. > > No, a collation implies a character repertoire like UCS (unicode), it can > apply t

Re: [HACKERS] charset/collation in values

2004-11-02 Thread Tatsuo Ishii
> Am Montag, 1. November 2004 07:41 schrieb Dennis Bjorklund: > > For each type we need to have convertion functions to and from strings. > > Any suggestion of how to represent these as strings now when it's a string > > plus two oid's? This is a though one.. > > A collation implies a character se

Re: [HACKERS] charset/collation in values

2004-11-02 Thread Dennis Bjorklund
On Tue, 2 Nov 2004, Peter Eisentraut wrote: > A collation implies a character set, so you only need to store one piece of > information anyway. No, a collation implies a character repertoire like UCS (unicode), it can apply to several character sets like UTF8 and UTF16. One can enumerate all co

Re: [HACKERS] charset/collation in values

2004-11-02 Thread Peter Eisentraut
Am Montag, 1. November 2004 07:41 schrieb Dennis Bjorklund: > For each type we need to have convertion functions to and from strings. > Any suggestion of how to represent these as strings now when it's a string > plus two oid's? This is a though one.. A collation implies a character set, so you on

Re: [HACKERS] charset/collation in values

2004-11-01 Thread Tom Lane
Tatsuo Ishii <[EMAIL PROTECTED]> writes: > Right. AFAIK nobody has proposed charsets/collations onto disk. Oh? Personally, I'd much sooner eat those few bytes than try to impose a regime where in-memory representation is different from on-disk. regards, tom lane

Re: [HACKERS] charset/collation in values

2004-11-01 Thread Thomas Hallgren
Tatsuo Ishii wrote: Right. AFAIK nobody has proposed charsets/collations onto disk. -- My apologies in that case. I triggered on Dennis wording "If we want to avoid storing charset/collation both in the column type and in each row, we would need an extra layer that transforms the Datums before th

Re: [HACKERS] charset/collation in values

2004-11-01 Thread Tatsuo Ishii
> On Mon, 1 Nov 2004, Tom Lane wrote: > > > > I think the number of charset/collation combinations will be relatively > > > few so perhaps it would be space efficient to maintain a table where > > > each combination is given an oid and have string values store that > > > rather than two separat

Re: [HACKERS] charset/collation in values

2004-11-01 Thread Dennis Bjorklund
On Mon, 1 Nov 2004, Tom Lane wrote: > > I think the number of charset/collation combinations will be relatively > > few so perhaps it would be space efficient to maintain a table where > > each combination is given an oid and have string values store that > > rather than two separate oid's? >

Re: [HACKERS] charset/collation in values

2004-11-01 Thread Tom Lane
Thomas Hallgren <[EMAIL PROTECTED]> writes: > I think the number of charset/collation combinations will be relatively > few so perhaps it would be space efficient to maintain a table where > each combination is given an oid and have string values store that > rather than two separate oid's? In

Re: [HACKERS] charset/collation in values

2004-11-01 Thread Thomas Hallgren
Dennis Bjorklund wrote: I've looked into storing charset/collation in the string values. This means that we change varchar/text/BpChar to be structures that have a charset oid field and a collation oid field, the rest of the Datum is the string data. I think the number of charset/collation combinat