From: Tom Lane Date: Sun, 29 Aug 2010 15:19:26 +0000 (+0000) Subject: Remove obsolete remark that PQprepare() is more flexible than PREPARE. X-Git-Tag: REL8_3_12~24 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=93a5ecc7dfefd6ba9097f83296c8750aeae73de1;p=postgresql 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 d12e511302..20d7065ba3 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -1,4 +1,4 @@ - + <application>libpq</application> - C Library @@ -1523,9 +1523,8 @@ PGresult *PQprepare(PGconn *conn, Prepared statements for use with PQexecPrepared can also be created by executing SQL statements. (But PQprepare - is more flexible since it does not require parameter types to be - pre-specified.) Also, although there is no libpq + endterm="sql-prepare-title"> statements. + Also, although there is no libpq function for deleting a prepared statement, the SQL statement can be used for that purpose.