It could be a pgAdmin III presentation fault.
I'm using PostgreSQL 8.0.0 on Windows 2k and I've got the same problem
but only when inquiring via pgAdmin, using psql from command line all
goes ok. I think that the resulting string are correct, that's why the
function "position(\'.\' in userName);" d
or (...)
Cathy
Burn ! <[EMAIL PROTECTED]>
Phone:
10/03/2005 08:43
To: pgsql-bugs@postgresql.org
cc: Cathy HEMSLEY/GBRUG03/APC/[EMAIL PROTECTED]
Subject: R: [BUGS] Fault when return strings over 256 characters in PLpgSQL
It coul
[EMAIL PROTECTED] wrote:
I have a PLpgSQL function that returns a string (varchar): if this string
is over 256 characters long then the last three characters are corrupted:
replaced by the string ' (.'
I'm skeptical: there is nothing special about 256 characters as far as
the varchar implementa
I have a PLpgSQL function that returns a string (varchar): if this string is over 256 characters long then the last three characters are corrupted: replaced by the string ' (.'
This is my test function:-
-- Function: testconverttousername(varchar, varchar)
DROP FUNCTION testconverttousername()