Done for ecpg:

< 	o Use backend PREPARE/EXECUTE facility for ecpg where possible
This commit is contained in:
Bruce Momjian 2007-08-14 17:02:42 +00:00
parent 002b4781ba
commit 6ccc262d6d
1 changed files with 2 additions and 2 deletions

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:bruce@momjian.us">bruce@momjian.us</a>)<br/>
Last updated: Wed Aug 1 19:13:20 EDT 2007
Last updated: Tue Aug 14 13:02:38 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>.
@ -802,7 +802,7 @@ first. There is also a developer's wiki at<br/>
</li><li>Solve cardinality &gt; 1 for input descriptors / variables?
</li><li>Add a semantic check level, e.g. check if a table really exists
</li><li>fix handling of DB attributes that are arrays
</li><li>Use backend PREPARE/EXECUTE facility for ecpg where possible
</li><li>-<em>Use backend PREPARE/EXECUTE facility for ecpg where possible</em>
</li><li>Implement SQLDA
</li><li>Fix nested C comments
</li><li>%sqlwarn[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?6">6</a>] should be 'W' if the PRECISION or SCALE value specified