backward compatible

Поиск
Список
Период
Сортировка
Искать

backward compatible

От:
Bruce Momjian <bruce@momjian.us>
Дата:
In docs, rename "backwards compatibility" to "backward compatibility"
for consistency.  Applied patch attached.

-- 
  Bruce Momjian          http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +
diff --git a/doc/src/sgml/array.sgml b/doc/src/sgml/array.sgml
new file mode 100644
index b3ecda5..bb318c5
*** a/doc/src/sgml/array.sgml
--- b/doc/src/sgml/array.sgml
*************** SELECT f1[1][-2][3] AS e1, f1[1][-1][5] 
*** 646,652 ****
     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
     pre-8.2 versions of PostgreSQL</>, the  configuration parameter can be turned
     off</> to suppress recognition of NULL</> as a NULL.
--- 646,652 ----
     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 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
new file mode 100644
index 0c682c8..a4c1e84
*** a/doc/src/sgml/config.sgml
--- b/doc/src/sgml/config.sgml
*************** dynamic_library_path = 'C:\tools\postgre
*** 5357,5363 ****
          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
          applications that require the old behavior, this variable can be
          turned off</>.
         
--- 5357,5363 ----
          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 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
new file mode 100644
index da45970..8b5c3c5
*** a/doc/src/sgml/func.sgml
--- b/doc/src/sgml/func.sgml
*************** nextval('foo')              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
      facility still exists, but internally it is now handled as an implicit
      coercion from text</> to regclass</> before the function is
      invoked.
--- 9695,9701 ----
      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 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
new file mode 100644
index 59b4011..195d83b
*** a/doc/src/sgml/libpq.sgml
--- b/doc/src/sgml/libpq.sgml
*************** char *PQport(const PGconn *conn);
*** 1313,1319 ****
         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.)
  
  
  char *PQtty(const PGconn *conn);
--- 1313,1319 ----
         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 backward compatibility.)
  
  
  char *PQtty(const PGconn *conn);
*************** ldap://ldap.acme.com/cn=dbserver,cn=host
*** 6933,6939 ****
     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.
    
  
   
--- 6933,6939 ----
     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 backward compatibility, and is not recommended in secure deployments.
    
  
   
diff --git a/doc/src/sgml/lobj.sgml b/doc/src/sgml/lobj.sgml
new file mode 100644
index 0e6b705..291409f
*** a/doc/src/sgml/lobj.sgml
--- b/doc/src/sgml/lobj.sgml
*************** Oid lo_creat(PGconn *conn, int mode);
*** 114,120 ****
  
       mode is unused and
       ignored as of PostgreSQL 8.1; however, for
!      backwards 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
--- 114,120 ----
  
       mode is unused and
       ignored as of PostgreSQL 8.1; however, for
!      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
new file mode 100644
index 16984aa..0aab10b
*** a/doc/src/sgml/plperl.sgml
--- b/doc/src/sgml/plperl.sgml
*************** select returns_array();
*** 202,208 ****
    
     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
     code written for PostgreSQL versions below 9.1 to
     run.  For example:
  
--- 202,208 ----
    
     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 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
new file mode 100644
index 1a3ebc6..d96ff77
*** a/doc/src/sgml/user-manag.sgml
--- b/doc/src/sgml/user-manag.sgml
*************** RESET ROLE;
*** 384,390 ****
      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
      releases in which users always had use of permissions granted to groups
      they were members of.
     
--- 384,390 ----
      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 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
new file mode 100644
index 1a35014..c8d8999
*** a/doc/src/sgml/xfunc.sgml
--- b/doc/src/sgml/xfunc.sgml
*************** CREATE FUNCTION test(int, int) RETURNS i
*** 1368,1374 ****
      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
      is accepted as meaning that the C-language function name is the
      same as the SQL name.)
     
--- 1368,1374 ----
      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 backward compatibility, an empty body
      is accepted as meaning that the C-language function name is the
      same as the SQL name.)
     
*************** typedef struct
*** 2701,2707 ****
      /*
       * OPTIONAL pointer to result slot
       *
!      * This is obsolete and only present for backwards compatibility, viz,
       * user-defined SRFs that use the deprecated TupleDescGetSlot().
       */
      TupleTableSlot *slot;
--- 2701,2707 ----
      /*
       * OPTIONAL pointer to result slot
       *
!      * This is obsolete and only present for backward compatibility, viz,
       * user-defined SRFs that use the deprecated TupleDescGetSlot().
       */
      TupleTableSlot *slot;
FAQ