X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 820E811F6089 for ; Tue, 25 Apr 2006 06:34:48 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 66093-06 for ; Tue, 25 Apr 2006 06:34:40 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sydney.mailnetwork.co.uk (server88-208-192-113.live-servers.net [88.208.192.113]) by postgresql.org (Postfix) with ESMTP id 9DA2D11F6083 for ; Tue, 25 Apr 2006 06:34:38 -0300 (ADT) Received: from [213.146.143.243] (port=23135 helo=it020361) by sydney.mailnetwork.co.uk with esmtpa (Exim 4.60) (envelope-from ) id 1FYJwG-0000Qb-Rb; Tue, 25 Apr 2006 10:34:33 +0100 Reply-To: From: "Andy Shellam" To: Cc: Subject: Re: Is it a bug ? Date: Tue, 25 Apr 2006 10:34:32 +0100 Organization: the mail network MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0015_01C66853.D750F860" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <200604250905.k3P950IQ010685@Citrus.usj.edu.lb> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 thread-index: AcZoPAuvtAL1fxDmSB6zFYZvsaQGDgACf9VwAAFUgdA= Message-Id: <20060425093438.9DA2D11F6083@postgresql.org> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/263 X-Sequence-Number: 21432 This is a multi-part message in MIME format. ------=_NextPart_000_0015_01C66853.D750F860 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi Pascal, 7.3 is now quite out-dated - have you tried the latest release, 8.1.3, to see if the problem is still present? Andy _____ From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Pascal Tufenkji Sent: 25 April 2006 10:02 am To: pgsql-admin@postgresql.org Subject: [ADMIN] Is it a bug ? Hi, I just noticed a bug in PostgreSQL 7.3.2 I don't know if it exists in other versions If I have a UNICODE database and I make the following query SELECT * FROM table where code like 'abcz%'; Or SELECT * FROM table where code like 'abcz_'; (or anything that ends with z% or z_) It gives the following error : ERROR: Invalid UNICODE character sequence found (0xc000) Other queries like SELECT * FROM table where code ilike 'abcz%'; SELECT * FROM table where code like '%abcz%'; Or the same query but in an SQL_ASCII database don't give the same error Is it a bug in Postgres ???? I'd appreciate an explanation Thx Pascal !DSPAM:14,444debdd33695139936371! ------=_NextPart_000_0015_01C66853.D750F860 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi = Pascal,

 

7.3 is now quite out-dated – = have you tried the latest release, 8.1.3, to see if the problem is still = present?

 

Andy

 


From: pgsql-admin-owner@postgresql.org = [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Pascal Tufenkji
Sent: 25 April 2006 10:02 = am
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Is it a = bug ?

 

Hi,

I just noticed a bug in = PostgreSQL 7.3.2

I don't know if it exists in = other versions

 

If I have a UNICODE database and = I make the following query

 

SELECT * FROM = table where code like 'abcz%';

Or =

SELECT * FROM = table where code like 'abcz_';

(or anything that ends with z% or = z_)

It gives the following error = :

ERROR:  Invalid UNICODE = character sequence found (0xc000)

 

Other queries like =

SELECT * FROM table where code = ilike 'abcz%';

SELECT * FROM table where code = like '%abcz%';

Or the same query but in = an SQL_ASCII database don’t = give the same error

 

Is it a bug in Postgres = ????

 

I’d appreciate an = explanation

 

Thx

Pascal

 

 

!DSPAM:14,444debdd33695139936371!

------=_NextPart_000_0015_01C66853.D750F860--