Seems no one wants this:

< * -Allow PREPARE to automatically determine parameter types based on the SQL < statement (Neil)

Seems no one wants this:
< * -Allow PREPARE to automatically determine parameter types based on the SQL < statement (Neil)
2a20412c · Bruce Momjian · c1d1c504 · 2a20412c · 2a20412c
隐藏空白更改
内联并排

Showing with 2 addition and 6 deletion

doc/TODO doc/TODO +1 -3

doc/src/FAQ/TODO.html doc/src/FAQ/TODO.html +1 -3

未找到文件。
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:	Bruce Momjian (bruce@momjian.us)
-Last updated:		Thu Sep 14 17:41:06 EDT 2006
+Last updated:		Thu Sep 14 17:43:58 EDT 2006

 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -449,8 +449,6 @@ SQL Commands
  called, and the table is locked in exclusive mode.

 * Allow PREPARE of cursors
-* -Allow PREPARE to automatically determine parameter types based on the SQL
-  statement (Neil)
 * Allow finer control over the caching of prepared query plans

  Currently, queries prepared via the libpq API are planned on first

--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -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:bruce@momjian.us">bruce@momjian.us</a>)<br/>
-Last updated:           Thu Sep 14 17:41:06 EDT 2006
+Last updated:           Thu Sep 14 17:43:58 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>.
@@ -411,8 +411,6 @@ first.
  called, and the table is locked in exclusive mode.
 </p>
  </li><li>Allow PREPARE of cursors
-  </li><li>-<em>Allow PREPARE to automatically determine parameter types based on the SQL</em>
-  statement (Neil)
  </li><li>Allow finer control over the caching of prepared query plans
 <p>  Currently, queries prepared via the libpq API are planned on first
  execute using the supplied parameters --- allow SQL PREPARE to do the