> Backspace deletes character-wise, as long as you have LANG set
> correctly. Check LANG and the LC_* environment variables.
OK, you're right:
$ echo $LANG
[EMAIL PROTECTED]
# show client_encoding ;
client_encoding
-
UTF8
(1 row)
But then I wonder why the client encoding is s
> "CN" == Csaba Nagy <[EMAIL PROTECTED]> writes:
CN> The full story is that I typed 'ü' (u-umlaut if it won't render
CN> correctly) and backspace before the '1'. I guess the backspace
CN> will delete byte-wise and will so fail to delete properly
CN> multi-byte characters.
Backspace deletes ch
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Yes, this appears to be a bug, not related to encoding etc. Maybe we
should be calling func_signature_string in generating this error.
Can't, because you don't have an Oid array for the types.
TypeNameToString is the correct th
Found a problem:
ereport(NOTICE,
(errmsg("function %s(%s) does not exist ... skipping",
NameListToString(functionName),
NameListToString(argTypes;
NameListToString() suppose as an argument List of Value nodes, but
argTypes is a l
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Yes, this appears to be a bug, not related to encoding etc. Maybe we
> should be calling func_signature_string in generating this error.
Can't, because you don't have an Oid array for the types.
TypeNameToString is the correct thing --- I'm considering
Teodor Sigaev wrote:
postgres=# drop type if exists foo;
NOTICE: type "foo" does not exist, skipping
DROP TYPE
postgres=# drop table if exists foo;
NOTICE: table "foo" does not exist, skipping
DROP TABLE
postgres=# drop function if exists foo();
NOTICE: function foo() does not exist ... skippi
postgres=# drop type if exists foo;
NOTICE: type "foo" does not exist, skipping
DROP TYPE
postgres=# drop table if exists foo;
NOTICE: table "foo" does not exist, skipping
DROP TABLE
postgres=# drop function if exists foo();
NOTICE: function foo() does not exist ... skipping
DROP FUNCTION
postg
Not being an expert, but to me it looks like the client_encoding being set to
UTF8 but the data being sent is something other than UTF8. I've seen this
happen on Linux when connecting with PuTTY from Windows (and then psql from the
linux machine) and having the wrong encoding set in PuTTY. I'd
Hi, Csaba,
Csaba Nagy wrote:
> dbval=# select 1;
> ERROR: column " 1" does not exist
>
> The full story is that I typed 'ü' (u-umlaut if it won't render
> correctly) and backspace before the '1'. I guess the backspace will
> delete byte-wise and will so fail to delete properly multi-byte
> cha
> Not being an expert, but to me it looks like the client_encoding being set to
> UTF8 but the data being sent is something other than UTF8. I've seen this
> happen on Linux when connecting with PuTTY from Windows (and then psql from
> the linux machine) and having the wrong encoding set in PuTT
> Linux:
>
> $ echo 'DROP FUNCTION if exists foo(int);' | psql 1c Timing is on.
> SET
> Time: 197.941 ms
> NOTICE: function foo(░) does not exist ... skipping
> ERROR: invalid byte sequence for encoding "UTF8": 0x90
> HINT: This error can also happen if the byte sequence does not
> match the en
Linux:
$ echo 'DROP FUNCTION if exists foo(int);' | psql 1c
Timing is on.
SET
Time: 197.941 ms
NOTICE: function foo(░) does not exist ... skipping
ERROR: invalid byte sequence for encoding "UTF8": 0x90
HINT: This error can also happen if the byte sequence does not match the
encoding expecte
12 matches
Mail list logo
