Hi Pascal,

 

If this is a bug in 7.3, and it’s not in later versions, I doubt the developers will be in any hurry to fix it, I don’t know – maybe someone knows a quick patch fix, or if it was fixed in a later version of the 7.3 series – as that would only be a minor upgrade (e.g. 7.3.2 to 7.3.8 or something), and it wouldn’t cause you much downtime.

 

Andy

 


From: Pascal Tufenkji [mailto:[EMAIL PROTECTED]
Sent: 25 April 2006 10:51 am
To: [EMAIL PROTECTED]
Subject: RE: [ADMIN] Is it a bug ?

 

Hi Andy

 

Actually no…

I just tried it on Postgres 8.0.4 and there is no problem

But is there no solution for the 7.3.0 version?

Because we haven’t upgraded our servers yet…

 

Thx for your quick reply

Pascal

 


From: Andy Shellam [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 25, 2006 12:35 PM
To: [EMAIL PROTECTED]
Cc: pgsql-admin@postgresql.org
Subject: RE: [ADMIN] Is it a bug ?

 

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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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,444df0ae33699570057613!

Reply via email to