database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-02 11:44:50 +03:00
Code

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:35 +00:00
parent 3f8e6c460e
commit e8254980df
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.220.2.7 2007/03/30 03:19:19 momjian Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.220.2.8 2010/08/29 15:19:35 tgl Exp $ -->
<chapter id="libpq">
<title><application>libpq</application> - C Library</title>
@ -1337,9 +1337,8 @@ about such errors.
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.