1berry/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove obsolete remark that PQprepare() is more flexible than PREPARE.

Browse Source 
Spotted by Dmitriy Igrishin.  Back-patch to 8.2, which is when the PREPARE
statement was improved to allow parameter types to be omitted.
This commit is contained in:
Tom Lane 2010-08-29 15:19:26 +00:00
parent 79beb90524
commit 93a5ecc7df
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/src/sgml/libpq.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.255.2.2 2008/11/04 22:36:12 momjian Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.255.2.3 2010/08/29 15:19:26 tgl Exp $ -->
<chapter id="libpq">
<title><application>libpq</application> - C Library</title>
@ -1523,9 +1523,8 @@ PGresult *PQprepare(PGconn *conn,
Prepared statements for use with <function>PQexecPrepared</> can also
be created by executing SQL <xref linkend="sql-prepare"
endterm="sql-prepare-title"> statements. (But <function>PQprepare</>
is more flexible since it does not require parameter types to be
pre-specified.) Also, although there is no <application>libpq</>
endterm="sql-prepare-title"> statements.
Also, although there is no <application>libpq</>
function for deleting a prepared statement, the SQL <xref
linkend="sql-deallocate" endterm="sql-deallocate-title"> statement
can be used for that purpose.