R: Fault when return strings over 256 characters in PLpgSQL
От | Burn ! |
---|---|
Тема | R: Fault when return strings over 256 characters in PLpgSQL |
Дата | |
Msg-id | 001a01c5254d$4d4fc4b0$5f733452@burn обсуждение исходный текст |
Ответ на | Re: Fault when return strings over 256 characters in PLpgSQL (Neil Conway <neilc@samurai.com>) |
Список | pgsql-bugs |
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);" doesn't find the dot. Matteo Brusamolin cathy.hemsley@powerconv.alstom.com 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 implementation is concerned, nor is the string ' (.' of any significance. Running your function (albeit on Linux) yields: neilc=# select testconverttousername(); testconverttousername ------------------------------------------------------------------------ ------------------------------------------------------------------------ ------------------------------------------------------------------------ -------------------------------------------- 123456781234567812345678123456781234567812345678123456781234567812345678 123456781234567812345678123456781234567812345678123456781234567812345678 123456781234567812345678123456781234567812345678123456781234567812345678 123456781234567812345678123456781234567888 (1 row) i.e. what one would expect. -Neil ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
В списке pgsql-bugs по дате отправления: