Re: not valid character for Unicode

On Fri, Jun 09, 2006 at 04:32:35PM +0100, Adam Witney wrote:
> > The database will do it for you. Note that the client encoding affects
> > input *and* output. So if you set it to latin1, the database will
> > convert all strings to latin1 before sending them to you...
>
> ok, so my current database (7.4.12) is UNICODE, but from psql when i run
> this

<snip>

> SELECT identifier from dba_data_base where bioassay_id = 1291 and
> identifier ilike '%G(at)S%';
> identifier
> --------------
> BG(at)S (0A11)
>
> so the mu chatacter is not showing up. So im not sure if the database is
> converting the output?

Is the character actually there? Do a length(identifier) on it to see
how many characters there are. When doing an interactive session it's
important that the client_encoding matches your display, otherwise you
might find it dropping characters or messing up in other ways.

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.