Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Bug in SQL for set returning functions
- From: Dave Page <dpage(at)postgresql(dot)org>
- To: Erwin Brandstetter <brandstetter(at)falter(dot)at>
- Cc: pgadmin-hackers(at)postgresql(dot)org
- Subject: Re: Bug in SQL for set returning functions
- Date: Fri, 27 Jul 2007 09:22:18 +0100
- Message-id: <46A9AB3A(dot)9060705(at)postgresql(dot)org>
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
- References:
- Bug in SQL for set returning functions
- From: Erwin Brandstetter
- Bug in SQL for set returning functions
- Prev by Date: SVN Commit by dpage: r6498 - trunk/pgadmin3/pgadmin/schema
- Next by Date: SVN Commit by dpage: r6499 - trunk/pgadmin3/pgadmin/frm
- Previous by thread: Bug in SQL for set returning functions
- Next by thread: SVN Commit by dpage: r6498 - trunk/pgadmin3/pgadmin/schema
- Indexes: