Skip to content

P
Postgres FD Implementation
Commit 3e8ff145 authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

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
parent 9a527f18
Show whitespace changes
Inline Side-by-side
Showing with 8 additions and 4 deletions
doc/TODO
View file @ 3e8ff145
...@@ -2,7 +2,7 @@ ...@@ -2,7 +2,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (bruce@momjian.us) 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 The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. http://www.postgresql.org/docs/faqs.TODO.html.
...@@ -751,9 +751,11 @@ SQL Commands ...@@ -751,9 +751,11 @@ SQL Commands
PL/pgSQL cursors should support the same syntax as PL/pgSQL cursors should support the same syntax as
backend cursors. backend cursors.
o Allow PL/RETURN to return row or record functions o Allow RETURN to return row or record functions
http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php 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
o Fix problems with RETURN NEXT on tables with o Fix problems with RETURN NEXT on tables with
dropped/added columns after function creation dropped/added columns after function creation
......
doc/src/FAQ/TODO.html
View file @ 3e8ff145
...@@ -8,7 +8,7 @@ ...@@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1> <h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/> <p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
Last updated: Mon Apr 2 13:18:40 EDT 2007 Last updated: Mon Apr 2 16:10:03 EDT 2007
</p> </p>
<p>The most recent version of this document can be viewed at<br/> <p>The most recent version of this document can be viewed at<br/>
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>. <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
...@@ -670,8 +670,10 @@ first. There is also a developer's wiki at<br/> ...@@ -670,8 +670,10 @@ first. There is also a developer's wiki at<br/>
<p> PL/pgSQL cursors should support the same syntax as <p> PL/pgSQL cursors should support the same syntax as
backend cursors. backend cursors.
</p> </p>
</li><li>Allow PL/RETURN to return row or record functions </li><li>Allow RETURN to return row or record functions
<p> <a href="http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php">http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php</a> <p> <a href="http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php">http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php</a>
<a href="http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php">http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php</a>
</p> </p>
</li><li>Fix problems with RETURN NEXT on tables with </li><li>Fix problems with RETURN NEXT on tables with
dropped/added columns after function creation dropped/added columns after function creation
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment