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
This commit is contained in:
parent
930930c476
commit
5db85688a5
@ -4052,7 +4052,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>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user