PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (bruce@momjian.us)
-Last updated: Fri Sep 7 15:07:48 EDT 2007
+Last updated: Fri Sep 14 14:50:43 EDT 2007
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
in the view, e.g. should SELECT * show additional columns if they
are added after the view is created.
+* Make it possible to use RETURNING together with conditional DO INSTEAD
+ rules, such as for partitioning setups
+
+ http://archives.postgresql.org/pgsql-hackers/2007-09/msg00577.php
+
SQL Commands
============
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<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/>
-Last updated: Fri Sep 7 15:07:48 EDT 2007
+Last updated: Fri Sep 14 14:50:43 EDT 2007
</p>
<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>.
<p> Another issue is whether underlying table changes should be reflected
in the view, e.g. should SELECT * show additional columns if they
are added after the view is created.
+</p>
+ </li><li>Make it possible to use RETURNING together with conditional DO INSTEAD
+ rules, such as for partitioning setups
+<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-09/msg00577.php">http://archives.postgresql.org/pgsql-hackers/2007-09/msg00577.php</a>
</p>
</li></ul>
<h1><a name="section_8">SQL Commands</a></h1>