From: Bruce Momjian Date: Fri, 11 Mar 2011 19:33:10 +0000 (-0500) Subject: In docs, rename "backwards compatibility" to "backward compatibility" X-Git-Tag: REL9_1_ALPHA5~96 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=7a8f43968add3c69b79c49ef236d945e643dcb1e;p=postgresql In docs, rename "backwards compatibility" to "backward compatibility" for consistency. --- diff --git a/doc/src/sgml/array.sgml b/doc/src/sgml/array.sgml index b3ecda5f25..bb318c5fc5 100644 --- a/doc/src/sgml/array.sgml +++ b/doc/src/sgml/array.sgml @@ -646,7 +646,7 @@ SELECT f1[1][-2][3] AS e1, f1[1][-1][5] AS e2 If the value written for an element is NULL (in any case variant), the element is taken to be NULL. The presence of any quotes or backslashes disables this and allows the literal string value - NULL to be entered. Also, for backwards compatibility with + NULL to be entered. Also, for backward compatibility with pre-8.2 versions of PostgreSQL, the configuration parameter can be turned off to suppress recognition of NULL as a NULL. diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 0c682c833b..a4c1e84ad8 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -5357,7 +5357,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' null values to be entered. However, PostgreSQL versions before 8.2 did not support null values in arrays, and therefore would treat NULL as specifying a normal array element with - the string value NULL. For backwards compatibility with + the string value NULL. For backward compatibility with applications that require the old behavior, this variable can be turned off. diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index da45970d47..8b5c3c51ae 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -9695,7 +9695,7 @@ nextval('foo') searches search path for fo Before PostgreSQL 8.1, the arguments of the sequence functions were of type text, not regclass, and the above-described conversion from a text string to an OID value would - happen at run time during each call. For backwards compatibility, this + happen at run time during each call. For backward compatibility, this facility still exists, but internally it is now handled as an implicit coercion from text to regclass before the function is invoked. diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 59b4011b3f..195d83ba68 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -1313,7 +1313,7 @@ char *PQport(const PGconn *conn); Returns the debug TTY of the connection. (This is obsolete, since the server no longer pays attention to the TTY setting, but the function remains - for backwards compatibility.) + for backward compatibility.) char *PQtty(const PGconn *conn); @@ -6933,7 +6933,7 @@ ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*) The default value for sslmode is prefer. As is shown in the table, this makes no sense from a security point of view, and it only promises performance overhead if possible. It is only provided as the default - for backwards compatibility, and is not recommended in secure deployments. + for backward compatibility, and is not recommended in secure deployments. diff --git a/doc/src/sgml/lobj.sgml b/doc/src/sgml/lobj.sgml index 0e6b705835..291409fde0 100644 --- a/doc/src/sgml/lobj.sgml +++ b/doc/src/sgml/lobj.sgml @@ -114,7 +114,7 @@ Oid lo_creat(PGconn *conn, int mode); mode is unused and ignored as of PostgreSQL 8.1; however, for - backwards compatibility with earlier releases it is best to + backward compatibility with earlier releases it is best to set it to INV_READ, INV_WRITE, or INV_READ | INV_WRITE. (These symbolic constants are defined diff --git a/doc/src/sgml/plperl.sgml b/doc/src/sgml/plperl.sgml index 16984aab63..0aab10bbd6 100644 --- a/doc/src/sgml/plperl.sgml +++ b/doc/src/sgml/plperl.sgml @@ -202,7 +202,7 @@ select returns_array(); Perl passes PostgreSQL arrays as a blessed PostgreSQL::InServer::ARRAY object. This object may be treated as an array - reference or a string, allowing for backwards compatibility with Perl + reference or a string, allowing for backward compatibility with Perl code written for PostgreSQL versions below 9.1 to run. For example: diff --git a/doc/src/sgml/user-manag.sgml b/doc/src/sgml/user-manag.sgml index 1a3ebc650d..d96ff77a04 100644 --- a/doc/src/sgml/user-manag.sgml +++ b/doc/src/sgml/user-manag.sgml @@ -384,7 +384,7 @@ RESET ROLE; roles being used as SQL roles the INHERIT attribute, while giving roles being used as SQL users the NOINHERIT attribute. However, PostgreSQL defaults to giving all roles - the INHERIT attribute, for backwards compatibility with pre-8.1 + the INHERIT attribute, for backward compatibility with pre-8.1 releases in which users always had use of permissions granted to groups they were members of. diff --git a/doc/src/sgml/xfunc.sgml b/doc/src/sgml/xfunc.sgml index 1a35014170..c8d8999659 100644 --- a/doc/src/sgml/xfunc.sgml +++ b/doc/src/sgml/xfunc.sgml @@ -1368,7 +1368,7 @@ CREATE FUNCTION test(int, int) RETURNS int The body of the function definition specifies the C-language name of the function, which need not be the same as the name being declared for SQL use. - (For reasons of backwards compatibility, an empty body + (For reasons of backward compatibility, an empty body is accepted as meaning that the C-language function name is the same as the SQL name.) @@ -2701,7 +2701,7 @@ typedef struct /* * OPTIONAL pointer to result slot * - * This is obsolete and only present for backwards compatibility, viz, + * This is obsolete and only present for backward compatibility, viz, * user-defined SRFs that use the deprecated TupleDescGetSlot(). */ TupleTableSlot *slot;