Hi developers!

I am testing pgAdmin III Beta 2 (Oct 3 2006, re: 5426:5427) on Windows
XP (latest patch level).

With the following test case I can reproduce the bug:

CREATE OR REPLACE FUNCTION f_test(IN i integer, OUT o integer) AS
$$
BEGIN
o := i*2;
END;
$$
LANGUAGE 'plpgsql' VOLATILE;

COMMENT ON FUNCTION f_test(integer) IS 'NOTE the
line break!';


Now, when I try to edit properties of this function (function name, for
instance), I get the following error:

An error has occurred:
Fehler: Funktion f_test(integer, integer) existiert nicht

(I am running a German Windows XP.)
If the comment does not contain line breaks the error does not occur.
This bug is present in v1.4.3 as well. During beta testing 1.6 I have
been able to narrow down the cause.


Regards
Erwin Brandstetter

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

> -----Original Message-----
> From: pgadmin-support-owner@postgresql.org
> [mailtogadmin-support-owner@postgresql.org] On Behalf Of
> Erwin Brandstetter
> Sent: 13 October 2006 20:35
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] Bug: edit properties of function
> with OUT-parameters and line break in comment
>
> Hi developers!
>
> I am testing pgAdmin III Beta 2 (Oct 3 2006, re: 5426:5427) on Windows
> XP (latest patch level).
>
> With the following test case I can reproduce the bug:
>
> CREATE OR REPLACE FUNCTION f_test(IN i integer, OUT o integer) AS
> $$
> BEGIN
> o := i*2;
> END;
> $$
> LANGUAGE 'plpgsql' VOLATILE;
>
> COMMENT ON FUNCTION f_test(integer) IS 'NOTE the
> line break!';
>
>
> Now, when I try to edit properties of this function (function
> name, for
> instance), I get the following error:
>
> An error has occurred:
> Fehler: Funktion f_test(integer, integer) existiert nicht
>
> (I am running a German Windows XP.)
> If the comment does not contain line breaks the error does not occur.
> This bug is present in v1.4.3 as well. During beta testing 1.6 I have
> been able to narrow down the cause.

Thanks - I've committed a fix for this to SVN.

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match