Re: BUG: ILIKE with single-byte encoding
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Rolf Jentsch <RJentsch(at)electronicpartner(dot)de>
- Cc: pgsql-bugs(at)postgresql(dot)org
- Subject: Re: BUG: ILIKE with single-byte encoding
- Date: Fri, 29 Feb 2008 22:28:19 -0500
- Message-id: <24984.1204342099@sss.pgh.pa.us> <text/plain>
Rolf Jentsch <RJentsch(at)electronicpartner(dot)de> writes:
> With PostgreSQL 8.3.0 the following bug has been introduced with the ILIKE or
> ~~* operator:
> In a database with single-byte encoding as LATIN1 the expression
> SELECT 'aü' ILIKE '%ü';
> returns false.
> For the single-byte case there are some places where a (signed) char
> value is compared to the return value auf tolower() which is an int.
Patch applied, thanks! It turns out there was a second bug on the very
same line: some machines have problems if the argument of tolower()
isn't explicitly cast to unsigned char ...
regards, tom lane
Home |
Main Index |
Thread Index