pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feeda "catch all" type ... such a thing?
5+ messages / 5 participants
[nested] [flat]
* a "catch all" type ... such a thing?
@ 2005-09-08 21:20 Marc G. Fournier <scrappy@postgresql.org>
0 siblings, 2 replies; 5+ messages in thread
From: Marc G. Fournier @ 2005-09-08 21:20 UTC (permalink / raw)
To: pgsql-sql
Are there any data types that can hold pretty much any type of character?
UTF-16 isn't supported (or its missing from teh docs), and UTF-8 doesn't
appear to have a big enough range ...
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: a "catch all" type ... such a thing?
@ 2005-09-09 06:09 Eugene E. <sad@bankir.ru>
parent: Marc G. Fournier <scrappy@postgresql.org>
1 sibling, 1 reply; 5+ messages in thread
From: Eugene E. @ 2005-09-09 06:09 UTC (permalink / raw)
To: Marc G. Fournier <scrappy@postgresql.org>; +Cc: pgsql-sql
Marc G. Fournier wrote:
>
> Are there any data types that can hold pretty much any type of
> character? UTF-16 isn't supported (or its missing from teh docs), and
> UTF-8 doesn't appear to have a big enough range ...
PLEASE Note: type of caracter is generally not a matter of _datatype_
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: a "catch all" type ... such a thing?
@ 2005-09-09 06:55 Michael Glaesemann <grzm@myrealbox.com>
parent: Eugene E. <sad@bankir.ru>
0 siblings, 0 replies; 5+ messages in thread
From: Michael Glaesemann @ 2005-09-09 06:55 UTC (permalink / raw)
To: Eugene E. <sad@bankir.ru>; +Cc: pgsql-sql
On Sep 9, 2005, at 3:09 PM, Eugene E. wrote:
> Marc G. Fournier wrote:
>
>> Are there any data types that can hold pretty much any type of
>> character? UTF-16 isn't supported (or its missing from teh docs),
>> and UTF-8 doesn't appear to have a big enough range ...
>>
>
> PLEASE Note: type of caracter is generally not a matter of _datatype_
That said, perhaps BYTEA would work. Not exactly the same as some
kind of text string though, as you could only use the BYTEA functions
for data manipulation. The SQLASCII encoding is *very* accepting, but
has its own issues, which a look in the archives will provide more info.
Michael Glaesemann
grzm myrealbox com
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: a "catch all" type ... such a thing?
@ 2005-09-10 18:43 Peter Eisentraut <peter_e@gmx.net>
parent: Marc G. Fournier <scrappy@postgresql.org>
1 sibling, 1 reply; 5+ messages in thread
From: Peter Eisentraut @ 2005-09-10 18:43 UTC (permalink / raw)
To: Marc G. Fournier <scrappy@postgresql.org>; +Cc: pgsql-sql
Marc G. Fournier wrote:
> Are there any data types that can hold pretty much any type of
> character? UTF-16 isn't supported (or its missing from teh docs), and
> UTF-8 doesn't appear to have a big enough range ...
UTF-8 has exactly the same "range" as UTF-16. In any case, the UTF-8
encoding in PostgreSQL is probably your best choice, unless you want to
dig into the weirdness that is MULE_INTERNAL.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: a "catch all" type ... such a thing?
@ 2005-09-11 03:54 Trent Shipley <tshipley@deru.com>
parent: Peter Eisentraut <peter_e@gmx.net>
0 siblings, 0 replies; 5+ messages in thread
From: Trent Shipley @ 2005-09-11 03:54 UTC (permalink / raw)
To: pgsql-sql
On Saturday 2005-09-10 11:43, Peter Eisentraut wrote:
> Marc G. Fournier wrote:
> > Are there any data types that can hold pretty much any type of
> > character? UTF-16 isn't supported (or its missing from teh docs), and
> > UTF-8 doesn't appear to have a big enough range ...
>
> UTF-8 has exactly the same "range" as UTF-16. In any case, the UTF-8
> encoding in PostgreSQL is probably your best choice, unless you want to
> dig into the weirdness that is MULE_INTERNAL.
The 8.1 beta documentation says that UTF-8 in earlier versions of Pg only
covered the first 16 bits of Unicode. Unfortunately "pure" Unicode uses 32
bits and (according to my Unicode Demystified) needed at least 21 (?) bits to
represent all the code points available in Unicode 3.x. (I think Unicode is
now in 4.x.)
This means that the code space supported by Pg 8.0 is technically too small.
It shouldn't matter though, unless you are working with Chinese or a private
character set.
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2005-09-11 03:54 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-09-08 21:20 a "catch all" type ... such a thing? Marc G. Fournier <scrappy@postgresql.org>
2005-09-09 06:09 ` Eugene E. <sad@bankir.ru>
2005-09-09 06:55 ` Michael Glaesemann <grzm@myrealbox.com>
2005-09-10 18:43 ` Peter Eisentraut <peter_e@gmx.net>
2005-09-11 03:54 ` Trent Shipley <tshipley@deru.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox