Commit d4888a3f authored by Bruce Momjian's avatar Bruce Momjian

doc: adjust libpq wording to be neither/nor

Reported-by: postgresql@cohi.at

Discussion: https://postgr.es/m/155419437926.737.10876947446993402227@wrigleys.postgresql.org

Backpatch-through: 9.4
parent f72d9a5e
...@@ -4153,7 +4153,7 @@ char *PQescapeLiteral(PGconn *conn, const char *str, size_t length); ...@@ -4153,7 +4153,7 @@ char *PQescapeLiteral(PGconn *conn, const char *str, size_t length);
</tip> </tip>
<para> <para>
Note that it is not necessary nor correct to do escaping when a data Note that it is neither necessary nor correct to do escaping when a data
value is passed as a separate parameter in <function>PQexecParams</function> or value is passed as a separate parameter in <function>PQexecParams</function> or
its sibling routines. its sibling routines.
</para> </para>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment