From: | Victor Snezhko <snezhko(at)indorsoft(dot)ru> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Volkan YAZICI <yazicivo(at)ttnet(dot)net(dot)tr>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #1931: ILIKE and LIKE fails on Turkish locale |
Date: | 2006-09-07 04:32:39 |
Message-ID: | uveo08ffc.fsf@indorsoft.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-tr-genel |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> Hmm, seems like plpgsql is also broken for multibyte encodings. it
>> contains some single-byte ops, like the following:
>
>> while (*s && isspace((unsigned char) *s))
>> s++;
>> if (*s++ != '.')
>> elog(ERROR, "expected dot between identifiers: %s", sstart);
>
> That code is not broken ... at least not unless isspace() is.
OK, sorry for the FUD, I'm just trying to find a cause... I will not
bring such ungrounded accusations next time.
But... maybe I misunderstand something fundamental, but should isspace
work when we pass one byte of multibyte character?
I'm digging this procedure (plpgsql_convert_ident()) and will report
if I find something wrong inside it and not inside isspace.
--
WBR, Victor V. Snezhko
E-mail: snezhko(at)indorsoft(dot)ru
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-09-07 04:36:32 | Re: BUG #1931: ILIKE and LIKE fails on Turkish locale |
Previous Message | Tom Lane | 2006-09-06 20:04:58 | Re: BUG #2600: dblink compile with SSL missing libraries |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-09-07 04:36:32 | Re: BUG #1931: ILIKE and LIKE fails on Turkish locale |
Previous Message | Timu EREN | 2006-09-07 02:47:24 | Re: Cursor ve Subselect yada Join... |