Victor Snezhko <[EMAIL PROTECTED]> writes:
> ERROR: expected dot between identifiers: х
> CONTEXT: compile of PL/pgSQL function "createoraltertable" near line 2
>
> the following query fails:
>
> CREATE OR REPLACE FUNCTION TestFunction()
> RETURNS int
> AS $$
> BEGIN
> SELECT х FROM test_table
Victor Snezhko <[EMAIL PROTECTED]> 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
Tom Lane <[EMAIL PROTECTED]> 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 d
Victor Snezhko <[EMAIL PROTECTED]> writes:
> But... maybe I misunderstand something fundamental, but should isspace
> work when we pass one byte of multibyte character?
Yes, it should, because we only allow ASCII-superset encodings inside
the backend. That is, characters that actually occupy mult
