[OGo-Users] umlauts with postgres 8.x and ogo 1.1.6

[Alexandre Ghisoli]

Le jeudi 25 janvier 2007 à 13:47 +0000, Sebastian Reitenbach a écrit :
> Hi all,
> 
> I upgraded ogo database from 7.x to 8.x, 
> 
> 
> when I now add an appointment, and have in the name, or location or 
> description words containing umlauts, then I get the following error message:
> 
> SKYRIX:
> appointment::new: PostgreSQL72FatalError fatal pgsql error 
> (channel=<0x0x88f832c[PostgreSQL72Channel]: 
> connection=<0x0xa6d33ac[PGConnection]:  connection=0x0xb1a25b8>>): 
> ERROR:  invalid byte sequence for encoding 'UTF8': 0xe4f6fc
> HINT:  This error can also happen if the byte sequence does not match the 
> encoding expected by the server, which is controlled by 'client_encoding'.
> 
> when I search for contacts, where the name contains umlauts, then I see the 
> following exception in the webui:
> 
> Application Server caught exception:
> 
>   session: 323132310545B87561
>   element: 06745b875670930552c.0.17.1.1.b.personSearch.3.1.2
>   context: <0x0x94933bc[WOContext]: 06845b8756a094933bc app=OpenGroupware 
> sn=323132310545B87561 eid=06745b875670930552c.0.17.1.1.b.personSearch.3.1.2 
> rqeid=06745b875670930552c.0.17.1.1.b.personSearch.3.1.2>
>   request: <WORequest[0x0x923da6c]: method=POST 
> uri=/OpenGroupware.woa/wo/323132310545B87561/06745b875670930552c.0.17.1.1.b.pers
> onSearch.3.1 
> app=OpenGroupware rqKey=wo 
> rqPath=323132310545B87561/06745b875670930552c.0.17.1.1.b.personSearch.3.1>
> 
>   class:   PostgreSQL72Exception
>   name:    PostgreSQL72FatalError
>   reason:  fatal pgsql error (channel=<0x0x91d3304[PostgreSQL72Channel]: 
> connection=<0x0x92f8bc4[PGConnection]:  connection=0x0x93cc418>>): ERROR:  
> invalid byte sequence for encoding "UTF8": 0xfc6c6c657225
> HINT:  This error can also happen if the byte sequence does not match the 
> encoding expected by the server, which is controlled by "client_encoding".
> 
>   info:
>     
> 
> I think I shall have to configure some "client_encoding", but I do not know 
> where and what the value should be. any hints?

Like Helge answers to my same question the 31 may 2006 :

" Run

   export PGCLIENTENCODING=LATIN1

prior starting the OGo process(es). Usually this is done by the 
RPM/Deb packages automagically?

The current SOPE 4.5 database adaptor uses Latin-1 when communicating 
with the database. "