From 3e8ff1450600f208587a721b03f9144ffb99c7dc Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Mon, 2 Apr 2007 20:10:16 +0000 Subject: Add URL for: o Allow RETURN to return row or record functions > o Allow RETURN to return row or record functions > http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php > http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php --- doc/src/FAQ/TODO.html | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 3dd19a18ad7..ca1ab59c374 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@

PostgreSQL TODO List

Current maintainer: Bruce Momjian (bruce@momjian.us)
-Last updated: Mon Apr 2 13:18:40 EDT 2007 +Last updated: Mon Apr 2 16:10:03 EDT 2007

The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. @@ -670,8 +670,10 @@ first. There is also a developer's wiki at

PL/pgSQL cursors should support the same syntax as backend cursors.

Allow PL/RETURN to return row or record functions +

Allow RETURN to return row or record functions

http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php + http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php + http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php

Fix problems with RETURN NEXT on tables with dropped/added columns after function creation -- cgit v1.2.3