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 8E10111F629C for ; Tue, 25 Apr 2006 06:27:01 -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 64328-04 for ; Tue, 25 Apr 2006 06:26:46 -0300 (ADT) X-Greylist: delayed 00:25:48.842632 by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 0DD6411F628C for ; Tue, 25 Apr 2006 06:26:40 -0300 (ADT) Received: from Citrus.usj.edu.lb (rectorat2.usj.edu.lb [193.227.187.140]) by svr4.postgresql.org (Postfix) with ESMTP id F26015B1FA9 for ; Tue, 25 Apr 2006 09:00:51 +0000 (GMT) Received: from pascolo ([192.168.100.239]) by Citrus.usj.edu.lb (8.13.1/8.13.1) with ESMTP id k3P950IQ010685 for ; Tue, 25 Apr 2006 12:05:04 +0300 Message-Id: <200604250905.k3P950IQ010685@Citrus.usj.edu.lb> Reply-To: From: "Pascal Tufenkji" To: Subject: Is it a bug ? Date: Tue, 25 Apr 2006 12:02:16 +0300 Organization: USJ MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_004F_01C66860.197DC5E0" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <13660.1145949556@sss.pgh.pa.us> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcZoPAuvtAL1fxDmSB6zFYZvsaQGDgACf9Vw X-USJ-MailScanner-Information: Please contact the ISP for more information X-USJ-MailScanner: Found to be clean X-USJ-MailScanner-From: ptufenkji@usj.edu.lb X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/262 X-Sequence-Number: 21431 This is a multi-part message in MIME format. ------=_NextPart_000_004F_01C66860.197DC5E0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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 ------=_NextPart_000_004F_01C66860.197DC5E0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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

 

 

------=_NextPart_000_004F_01C66860.197DC5E0--