Thread: PQescapeLiteral(), PQescapeIdentifier() documented with invalid signatures.
PQescapeLiteral(), PQescapeIdentifier() documented with invalid signatures.
From
Dmitriy Igrishin
Date:
Hey all,
Actual signatures of libpq's functions PQescapeLiteral(), PQescapeIdentifier()
is
char *PQescapeLiteral(PGconn *conn, const char *str, size_t len)
char *PQescapeIdentifier(PGconn *conn, const char *str, size_t len)
that differs from signatures provided in the documentation here
http://www.postgresql.org/docs/9.0/static/libpq-exec.html#LIBPQ-EXEC-ESCAPE-STRING
Regards,
Dmitriy
Actual signatures of libpq's functions PQescapeLiteral(), PQescapeIdentifier()
is
char *PQescapeLiteral(PGconn *conn, const char *str, size_t len)
char *PQescapeIdentifier(PGconn *conn, const char *str, size_t len)
that differs from signatures provided in the documentation here
http://www.postgresql.org/docs/9.0/static/libpq-exec.html#LIBPQ-EXEC-ESCAPE-STRING
Regards,
Dmitriy
Dmitriy Igrishin <dmitigr@gmail.com> writes: > Actual signatures of libpq's functions PQescapeLiteral(), > PQescapeIdentifier() > is > char *PQescapeLiteral(PGconn *conn, const char *str, size_t len) > char *PQescapeIdentifier(PGconn *conn, const char *str, size_t len) > that differs from signatures provided in the documentation here > http://www.postgresql.org/docs/9.0/static/libpq-exec.html#LIBPQ-EXEC-ESCAPE-STRING Wow ... I can understand missing the "const" declarations, but getting the return type wrong is pretty bad :-(. Amazing nobody caught this before. Thanks, will fix! regards, tom lane