DateStyle>,
TimeZone>,
integer_datetimes>, and
-standard_compliant_strings>.
+standard_conforming_strings>.
(server_encoding>, TimeZone>, and
integer_datetimes> were not reported by releases before 8.0;
-standard_compliant_strings> was not reported by releases
+standard_conforming_strings> was not reported by releases
before 8.1.)
Note that
server_version>,
-If no value for standard_compliant_strings> is reported,
+If no value for standard_conforming_strings> is reported,
applications may assume it is 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
-
+
Frontend/Backend Protocol
DateStyle>,
TimeZone>,
integer_datetimes>, and
- standard_compliant_strings>.
+ standard_conforming_strings>.
(server_encoding>, TimeZone>, and
integer_datetimes> were not reported by releases before 8.0;
- standard_compliant_strings> was not reported by releases
+ standard_conforming_strings> was not reported by releases
before 8.1.)
Note that
server_version>,
Escape string syntax (E'...'>) should be used for
escapes, because in future versions of
PostgreSQL ordinary strings will have
- the standard-compliant behavior of treating backslashes
+ the standard-conforming behavior of treating backslashes
literally.
- mpliant-strings" xreflabel="standard_compliant_strings">
- standard_compliant_strings (boolean)
+ nforming-strings" xreflabel="standard_conforming_strings">
+ standard_conforming_strings (boolean)
-
standard_compliant_strings> configuration parameter
+
standard_conforming_strings> configuration parameter
While ordinary strings now support C-style backslash escapes,
future versions will generate warnings for such usage and
eventually treat backslashes as literal characters to be
- standard-compliant. The proper way to specify escape processing is
+ standard-conforming. The proper way to specify escape processing is
to use the escape string syntax to indicate that escape
processing is desired. Escape string syntax is specified by writing
the letter E (upper or lower case) just before
* Written by Peter Eisentraut
.
*
* IDENTIFICATION
- * $PostgreSQL: pgsql/src/backend/utils/misc/guc.c,v 1.281 2005/08/11 21:11:47 tgl Exp $
+ * $PostgreSQL: pgsql/src/backend/utils/misc/guc.c,v 1.282 2005/08/14 22:19:50 petere Exp $
*
*--------------------------------------------------------------------
*/
static int max_identifier_length;
static int block_size;
static bool integer_datetimes;
-static bool standard_compliant_strings;
+static bool standard_conforming_strings;
/* should be static, but commands/variable.c needs to get at these */
char *role_string;
},
{
- {"standard_compliant_strings", PGC_INTERNAL, PRESET_OPTIONS,
+ {"standard_conforming_strings", PGC_INTERNAL, PRESET_OPTIONS,
gettext_noop("'...' strings treat backslashes literally."),
NULL,
GUC_REPORT | GUC_NOT_IN_SAMPLE | GUC_DISALLOW_IN_FILE
},
- &standard_compliant_strings,
+ &standard_conforming_strings,
false, NULL, NULL
},