Re: encoding bug or feature?

From: marcelo Cortez <jmdc_marcelo(at)yahoo(dot)com(dot)ar>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jorge Godoy <jgodoy(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: encoding bug or feature?
Date: 2006-07-11 19:36:30
Message-ID: 20060711193630.36270.qmail@web32101.mail.mud.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom , folks

I've recreated the database with --locale=es_AR
keyword
and all works fine

thanks a lot.

best
MDC

--- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> escribió:

> marcelo Cortez <jmdc_marcelo(at)yahoo(dot)com(dot)ar> writes:
> > testutf8=# \set
> > ...
> > ENCODING = 'UTF8'
> > HISTSIZE = '500'
> > testutf8=# select upper('ñ');
> > ERROR: invalid UTF-8 byte sequence detected near
> byte
> > 0xf1
> > testutf8=#
>
> You're telling the system that your client encoding
> is utf8, but
> it looks from here like you're using some LatinN
> encoding.
> Try "\encoding latin1" or whatever it is your
> keyboard is generating.
>
> regards, tom lane
>




___________________________________________________________
1GB gratis, Antivirus y Antispam
Correo Yahoo!, el mejor correo web del mundo
http://correo.yahoo.com.ar

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jan Wieck 2006-07-11 19:48:26 Re: Help making a plpgsql function?
Previous Message Merlin Moncure 2006-07-11 19:31:23 Re: pgsql vs mysql