diff options
Diffstat (limited to 'doc/src/sgml/libpq.sgml')
| -rw-r--r-- | doc/src/sgml/libpq.sgml | 21 |
1 files changed, 16 insertions, 5 deletions
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 9c1b94e2be7..a5bde7fc76e 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -1,5 +1,5 @@ <!-- -$PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.186 2005/06/21 04:02:29 tgl Exp $ +$PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.187 2005/06/26 19:16:04 tgl Exp $ --> <chapter id="libpq"> @@ -286,7 +286,7 @@ PGconn *PQconnectdb(const char *conninfo); Kerberos service name to use when authenticating with Kerberos 4 or 5. This must match the service name specified in the server configuration for Kerberos authentication to succeed. (See also - <xref linkend="kerberos-auth">.) + <xref linkend="kerberos-auth">.) </para> </listitem> </varlistentry> @@ -888,10 +888,13 @@ Parameters reported as of the current release include <literal>is_superuser</>, <literal>session_authorization</>, <literal>DateStyle</>, -<literal>TimeZone</>, and -<literal>integer_datetimes</>. +<literal>TimeZone</>, +<literal>integer_datetimes</>, and +<literal>standard_compliant_strings</>. (<literal>server_encoding</>, <literal>TimeZone</>, and -<literal>integer_datetimes</> were not reported by releases before 8.0.) +<literal>integer_datetimes</> were not reported by releases before 8.0; +<literal>standard_compliant_strings</> was not reported by releases +before 8.1.) Note that <literal>server_version</>, <literal>server_encoding</> and @@ -914,6 +917,14 @@ in a numeric form that is much easier to compare against. </para> <para> +If no value for <literal>standard_compliant_strings</> is reported, +applications may assume it is <literal>false</>, that is, backslashes +are treated as escapes in string literals. Also, the presence of this +parameter may be taken as an indication that the escape string syntax +(<literal>E'...'</>) is accepted. +</para> + +<para> Although the returned pointer is declared <literal>const</>, it in fact points to mutable storage associated with the <literal>PGconn</> structure. It is unwise to assume the pointer will remain valid across queries. |