Hello,
I`m using postgresql 7.2.1. According to the following lines data in
my database gets encoded as unicode. Server and client communication
seems to use unicode as well:
woody=# select version();
version
---
PostgreSQL 7.2.1 on i686
Fritz Bayer wrote:
> I have a java program, which writes words containing german umlauts
> like äöü into the database. As you probably know, those characters
> belong to the ISO-8859-1 character encoding set.
>
> In my java webapplication those umlauts (äöü) get displayed correctly.
> So
Fritz Bayer wrote:
Hello,
I`m using postgresql 7.2.1. According to the following lines data in
my database gets encoded as unicode. Server and client communication
seems to use unicode as well:
woody=# select version();
version
---
Postgre
[EMAIL PROTECTED] ("Magnus Naeslund(t)") wrote in message news:<[EMAIL
PROTECTED]>...
> Fritz Bayer wrote:
> > Hello,
> >
> > I`m using postgresql 7.2.1. According to the following lines data in
> > my database gets encoded as unicode. Server and client communication
> > seems to use unicode as w
[EMAIL PROTECTED] ("Daniel Verite") wrote in message news:<[EMAIL PROTECTED]>...
> Fritz Bayer wrote:
>
> > I have a java program, which writes words containing german umlauts
> > like äöü into the database. As you probably know, those characters
> > belong to the ISO-8859-1 character encoding set
On Apr 12, 2005, at 6:39 AM, Fritz Bayer wrote:
But in which encoding? I guess utf8 or utf16...
But why doesn that fail only for äüö? Shouldn't any other letter
encoded in utf16 also fail?
I mean unicode itself is 16 bit long. So "münchen" should expand to 14
characters. But only ü expands to two c
On Tue, Apr 12, 2005 at 03:39:45AM -0700,
Fritz Bayer <[EMAIL PROTECTED]> wrote
a message of 53 lines which said:
> I mean unicode itself is 16 bit long.
This is completely false. Unicode itself is just a table and, since it
contains more than 100,000 characters, you cannot index them with 16
