= show client_encoding ;
client_encoding
-
UNICODE
(1 ligne)
= select char_length('a'), bit_length('a');
char_length | bit_length
-+
1 | 8
(1 ligne)
# that's an accented e
= select char_length('é'), bit_length('é'); ;
char_length |
I'm new to PostgreSQL, and from the looks of it, it's a great database,
and I'll be using more of it in the future.
I had a quick question if anyone could clear this up. The documentation
for PostgreSQL (version 7.1, the version this server is using) says that
it supports multibyte character
At 8:39 PM -0400 9/16/04, Richard Connamacher wrote:
I'm new to PostgreSQL, and from the looks of it, it's a great database,
and I'll be using more of it in the future.
I had a quick question if anyone could clear this up. The documentation
for PostgreSQL (version 7.1, the version this server is
On Sep 17, 2004, at 9:39 AM, Richard Connamacher wrote:
UTF-8 is the 8-bit version of Unicode.
The multibyte version of Unicode is UTF-16.
UTF-8 encodes characters with varying numbers of bytes, not just 1 byte
per character. IIRC, it's anywhere from 1 to 5 bytes, actually.
PostgreSQL uses
Thanks to both Dan Sugalski and Michael Glaesemann for answering my
question. I probably should have realized that, while Latin letters are
one byte, the fact that others are encoded into up to 5-byte groups
qualifies it as a multi-byte encoding. I don't anticipate having very
many non-latin
Richard Connamacher [EMAIL PROTECTED] writes:
7.1 may be prehistoric, but it's running on an off-site server that I'm
renting, and this version came pre-installed. Since it's already there
and working, I'd like to get familiar with it before I try to reinstall
a newer version. I doubt I'd know
