Обсуждение: Bug in SQL for set returning functions
Hi developers! Testing the pgAdmin III 1.8.0 Beta 2 (Jul 25 2007, rev: 6486). Client Win XP, host: Debian Sarge / PG 8.1.8 and Debian Etch / PG 8.2.4 I am afraid beta2 has introduced a new bug in the reverse engineering of SQL code. SET returning functions get two instances of the the "RETURNS " clause. Like this: CREATE OR REPLACE FUNCTION f_demofunc(IN integer, OUT integer) RETURNS SETOF record RETURNS SETOF record AS $BODY$ ... Does not seem to happen with simple return types. Regards Erwin
Erwin Brandstetter wrote: > Hi developers! > > Testing the pgAdmin III 1.8.0 Beta 2 (Jul 25 2007, rev: 6486). Client > Win XP, host: Debian Sarge / PG 8.1.8 and Debian Etch / PG 8.2.4 > > > I am afraid beta2 has introduced a new bug in the reverse engineering of > SQL code. SET returning functions get two instances of the the "RETURNS > " clause. Like this: > > CREATE OR REPLACE FUNCTION f_demofunc(IN integer, OUT integer) > RETURNS SETOF record > RETURNS SETOF record AS > $BODY$ > ... My bad - fixed in SVN, thanks. Regards, Dave