pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Marcelo . <wachaca@yahoo.com>
To: pgsql-sql@postgresql.org
Subject: UTF8 Vs Latin9 and valid encoding.
Date: Tue, 29 Aug 2006 21:48:53 -0700 (PDT)
Message-ID: <20060830044853.15728.qmail@web53007.mail.yahoo.com> (raw)


Hello,
I am using postgres 8.1 for windows and have the
following dilema.

I have 2 databases, one encoded in UTF-8 and one in
Latin9.
In both DBs I can create the following test table:

CREATE TABLE "holaniño"
(
  nombre varchar(5),
  "titúlo" varchar(10)
) 
WITHOUT OIDS;

Then in both DBs I can execute the following SQL:

select * from holaniño where titúlo = 'compania'

HOWEVER, when I change the SQL to:
select * from holaniño where titúlo = "compañia"

(changed the N to a Ñ in the filter)
I receive the error msg:
ERROR:  invalid UTF-8 byte sequence detected near byte
0xf1

Where in the LATIN9 db, there is no problem.

Isn't UTF-8 the same as UNICODE where it encapsulates
all other coding schemes including latin9?

Any insight would be greatly apreciated.





__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 



view thread (3+ messages)  latest in thread

Message-ID: <20060830044853.15728.qmail@web53007.mail.yahoo.com>
Permalink:  ../20060830044853.15728.qmail@web53007.mail.yahoo.com/
Also on:    postgresql.org/message-id/20060830044853.15728.qmail@web53007.mail.yahoo.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: wachaca@yahoo.com
  Subject: Re: UTF8 Vs Latin9 and valid encoding.
  In-Reply-To: <20060830044853.15728.qmail@web53007.mail.yahoo.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox