DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=h5ARSCgaFXc97iPWL/dGsbDy7tSGdNcXyYDjKTp8EiegoBlbXpNrY8PBwhmBS6lTGtbl6P/DGyH1lSXCEaK26b0cISWkzKhz7G5/mmpsmHUI0SePhdqudZlmUgQmw5CVFzB6knbP0Ga7l88F26y3v4Oqk+DRwFfXf5o3auUzpO4=
	;
Message-ID: <20060830044853.15728.qmail@web53007.mail.yahoo.com>
Date: Tue, 29 Aug 2006 21:48:53 -0700 (PDT)
From: "Marcelo ." <wachaca@yahoo.com>
Subject: UTF8 Vs Latin9 and valid encoding.
To: pgsql-sql@postgresql.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit


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