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 3f9311f30dd47b48f3ad311ff81d2645baad49f5..c1ce6c30789bb108d0e04fa265e137ed6dcedf02 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.289.2.6 2010/08/10 02:57:19 rhaas Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.289.2.7 2010/08/29 15:19:19 tgl Exp $ -->
 
 <chapter id="libpq">
  <title><application>libpq</application> - C Library</title>
@@ -1706,9 +1706,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.