rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update wording: 

< * Add SQL99 WITH RECURSIVE to SELECT
> * Add SQL99 WITH RECURSIVE (hierarchical) queries to SELECT
This commit is contained in:
Bruce Momjian 2006-06-08 01:08:45 +00:00
parent 0f1a7c55b4
commit 8a75c07626
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/TODO
View File

@ -2,7 +2,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Last updated: Wed Jun 7 21:02:47 EDT 2006
Last updated: Wed Jun 7 21:08:40 EDT 2006
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@ -478,7 +478,7 @@ SQL Commands
to allow a higher range of values
* Make CLUSTER preserve recently-dead tuples per MVCC requirements
* Add SQL99 WITH clause to SELECT
* Add SQL99 WITH RECURSIVE to SELECT
* Add SQL99 WITH RECURSIVE (hierarchical) queries to SELECT
* Add DEFAULT .. AS OWNER so permission checks are done as the table
owner

4
doc/src/FAQ/TODO.html
View File

@ -8,7 +8,7 @@
<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:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
Last updated: Wed Jun 7 21:02:47 EDT 2006
Last updated: Wed Jun 7 21:08:40 EDT 2006
</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>.
@ -440,7 +440,7 @@ first.
to allow a higher range of values
</li><li>Make CLUSTER preserve recently-dead tuples per MVCC requirements
</li><li>Add SQL99 WITH clause to SELECT
</li><li>Add SQL99 WITH RECURSIVE to SELECT
</li><li>Add SQL99 WITH RECURSIVE (hierarchical) queries to SELECT
</li><li>Add DEFAULT .. AS OWNER so permission checks are done as the table
owner
<p> This would be useful for SERIAL nextval() calls and CHECK constraints.