Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commita9a999b

Browse files
committed
Remove obsolete remark that PQprepare() is more flexible than PREPARE.
Spotted by Dmitriy Igrishin. Back-patch to 8.2, which is when the PREPAREstatement was improved to allow parameter types to be omitted.
1 parent462583b commita9a999b

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

‎doc/src/sgml/libpq.sgml

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.321 2010/08/17 04:37:20 petere Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.322 2010/08/29 15:19:05 tgl Exp $ -->
22

33
<chapter id="libpq">
44
<title><application>libpq</application> - C Library</title>
@@ -1895,9 +1895,7 @@ PGresult *PQprepare(PGconn *conn,
18951895

18961896
Prepared statements for use with <function>PQexecPrepared</> can also
18971897
be created by executing SQL <xref linkend="sql-prepare">
1898-
statements. (But <function>PQprepare</>
1899-
is more flexible since it does not require parameter types to be
1900-
pre-specified.) Also, although there is no <application>libpq</>
1898+
statements. Also, although there is no <application>libpq</>
19011899
function for deleting a prepared statement, the SQL <xref
19021900
linkend="sql-deallocate"> statement
19031901
can be used for that purpose.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp