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

Spotted by Dmitriy Igrishin.  Back-patch to 8.2, which is when the PREPARE
statement was improved to allow parameter types to be omitted.

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 9aa7961cf861e392d411a0fe797e84f7d4ad5d3d..ea6865da98b3e66507c085d516c4fc673e5514c2 100644 (file)
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -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.