Terminology cleanup: class -> table, instance -> row, attribute -> column,

etc.

Author: petere

doc/src/sgml/admin.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/admin.sgml,v 1.28 2000/11/24 17:44:21 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/Attic/admin.sgml,v 1.29 2001/01/13 23:58:55 petere Exp $
 -->
 
 <book id="admin">
@@ -35,7 +35,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/admin.sgml,v 1.28 2000/11/24 17:44:21
    developed originally in the UC Berkeley Computer Science Department,
    pioneered many of the object-relational concepts
    now becoming available in some commercial databases.
-   It provides SQL92/SQL3 language support,
+   It provides SQL92/SQL99 language support,
    transaction integrity, and type extensibility.
    <productname>PostgreSQL</productname> is an open-source descendant
    of this original Berkeley code.

doc/src/sgml/advanced.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/advanced.sgml,v 1.20 2001/01/05 06:34:15 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/advanced.sgml,v 1.21 2001/01/13 23:58:55 petere Exp $
 -->
 
  <chapter id="advanced">
@@ -22,14 +22,14 @@ $Header: /cvsroot/pgsql/doc/src/sgml/advanced.sgml,v 1.20 2001/01/05 06:34:15 tg
    <title>Inheritance</title>
 
    <para>
-    Let's create two classes. The capitals  class  contains
+    Let's create two tables. The capitals  table  contains
     state  capitals  that  are also cities. Naturally, the
-    capitals class should inherit from cities.
+    capitals table should inherit from cities.
 
     <programlisting>
 CREATE TABLE cities (
     name            text,
-    population      float,
+    population      real,
     altitude        int     -- (in ft)
 );
 
@@ -38,20 +38,19 @@ CREATE TABLE capitals (
 ) INHERITS (cities);
     </programlisting>
 
-    In this case, an  instance  of  capitals  <firstterm>inherits</firstterm>  all
-    attributes  (name,  population,  and altitude) from its
-    parent, cities.  The type  of  the  attribute  name  is
+    In this case, a row  of  capitals  <firstterm>inherits</firstterm>  all
+    columns (name,  population,  and altitude) from its
+    parent, cities.  The type  of  the  column name  is
     <type>text</type>,  a  native  <productname>Postgres</productname>
     type  for variable length
-    ASCII strings.  The type of the attribute population is
-    <type>float</type>,  a  native <productname>Postgres</productname>
-    type for double precision
+    ASCII strings.  The type of the column population is
+    <type>real</type>,  a  type for single precision
     floating point numbers.  State capitals have  an  extra
-    attribute, state, that shows their state.
+    column, state, that shows their state.
     In <productname>Postgres</productname>,
-    a  class  can inherit from zero or more other classes,
-    and a query can reference either  all  instances  of  a
-    class  or  all  instances  of  a  class plus all of its
+    a  table  can inherit from zero or more other tables,
+    and a query can reference either  all  rows  of  a
+    table  or  all  rows  of  a  tables plus all of its
     descendants.
 
     <note>
@@ -109,7 +108,7 @@ SELECT name, altitude
 
    <para>
     Here the <quote>ONLY</quote> before cities indicates that the query should
-    be  run over only the cities table, and not classes below cities in the
+    be  run over only the cities table, and not tables below cities in the
     inheritance hierarchy.  Many of the  commands  that  we
     have  already discussed -- <command>SELECT</command>,
     <command>UPDATE</command> and <command>DELETE</command> --
@@ -122,7 +121,7 @@ SELECT name, altitude
      In previous versions of <productname>Postgres</productname>, the
      default was not to get access to child tables. This was found to
      be error prone and is also in violation of SQL99. Under the old
-     syntax, to get the sub-classes you append "*" to the table name.
+     syntax, to get the sub-tables you append "*" to the table name.
      For example
 <programlisting>
 SELECT * from cities*;
@@ -147,38 +146,38 @@ SET SQL_Inheritance TO OFF;
 
    <para>
     One  of  the tenets of the relational model is that the
-    attributes of a relation are atomic.
+    columns of a table are atomic.
     <productname>Postgres</productname> does not
-    have  this  restriction; attributes can themselves contain 
+    have  this  restriction; columns can themselves contain 
     sub-values that can be  accessed  from  the  query
-    language.   For example, you can create attributes that
+    language.   For example, you can create columns that
     are arrays of base types.
    </para>
 
    <sect2>
     <title>Arrays</title>
 
     <para>
-     <productname>Postgres</productname> allows attributes of an
-     instance to be defined
+     <productname>Postgres</productname> allows columns of a
+     row to be defined
      as  fixed-length  or  variable-length multi-dimensional
      arrays. Arrays of any base type  or  user-defined  type
      can  be created. To illustrate their use, we first create a 
-     class with arrays of base types.
+     table with arrays of base types.
 
      <programlisting>
 CREATE TABLE SAL_EMP (
     name            text,
-    pay_by_quarter  int4[],
+    pay_by_quarter  integer[],
     schedule        text[][]
 );
      </programlisting>
     </para>
 
     <para>
-     The above query will create a class named SAL_EMP  with
+     The above query will create a table named SAL_EMP  with
      a  <firstterm>text</firstterm>  string (name), a one-dimensional
-     array of <firstterm>int4</firstterm>
+     array of <firstterm>integer</firstterm>
      (pay_by_quarter),  which  represents   the   employee's
      salary by quarter and a two-dimensional array of
      <firstterm>text</firstterm>

doc/src/sgml/array.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/array.sgml,v 1.8 2000/12/18 23:39:37 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/array.sgml,v 1.9 2001/01/13 23:58:55 petere Exp $
 -->
 
 <Chapter Id="arrays">
@@ -14,10 +14,10 @@ This must become a chapter on array behavior. Volunteers? - thomas 1998-01-12
 </Para>
 
 <Para>
-     <ProductName>Postgres</ProductName> allows attributes of a class
+     <ProductName>Postgres</ProductName> allows columns of a table
      to be defined as variable-length multi-dimensional
      arrays. Arrays of any built-in type  or  user-defined  type
-     can  be created.  To illustrate their use, we create this class:
+     can  be created.  To illustrate their use, we create this table:
 
 <ProgramListing>
 CREATE TABLE sal_emp (
@@ -29,7 +29,7 @@ CREATE TABLE sal_emp (
 </Para>
 
 <Para>
-     The above query will create a class named <FirstTerm>sal_emp</FirstTerm>  with
+     The above query will create a table named <FirstTerm>sal_emp</FirstTerm>  with
      a  <FirstTerm>text</FirstTerm>  string (name), a one-dimensional array of <FirstTerm>int4</FirstTerm>
      (pay_by_quarter),  which  represents   the   employee's
      salary by quarter, and a two-dimensional array of <FirstTerm>text</FirstTerm>

doc/src/sgml/extend.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.8 2000/12/26 00:10:37 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.9 2001/01/13 23:58:55 petere Exp $
 -->
 
  <chapter id="extend">
@@ -44,15 +44,15 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.8 2000/12/26 00:10:37 peter
     about  databases,  tables,  columns,  etc., in what are
     commonly known as system catalogs.  (Some systems  call
     this  the data dictionary).  The catalogs appear to the
-    user as classes, like any other, but  the  <acronym>DBMS</acronym>  stores
+    user as tables like any other, but  the  <acronym>DBMS</acronym>  stores
     its  internal  bookkeeping in them.  One key difference
     between <productname>Postgres</productname> and  standard  relational  systems  is
     that <productname>Postgres</productname> stores much more information in its 
     catalogs -- not only information about tables and  columns,
     but also information about its types, functions, access
-    methods, and so on.  These classes can be  modified  by
+    methods, and so on.  These tables can be  modified  by
     the  user, and since <productname>Postgres</productname> bases its internal operation 
-    on these classes, this means that <productname>Postgres</productname> can  be
+    on these tables, this means that <productname>Postgres</productname> can  be
     extended   by   users.    By  comparison,  conventional
     database systems can only be extended by changing hardcoded  
     procedures within the <acronym>DBMS</acronym> or by loading modules
@@ -87,13 +87,13 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.8 2000/12/26 00:10:37 peter
     by  the  user and only understands the behavior of such
     types to the extent that the user describes them.  
     Composite  types  are  created whenever the user creates a
-    class.  EMP is an example of a composite  type.   
+    table.  EMP is an example of a composite  type.   
    </para>
 
    <para>
     <productname>Postgres</productname>  stores  these  types
     in only one way (within the
-    file that stores all instances of the  class)  but  the
+    file that stores all rows of a table)  but  the
     user can "look inside" at the attributes of these types
     from the query language and optimize their retrieval by
     (for example) defining indices on the attributes.
@@ -119,7 +119,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.8 2000/12/26 00:10:37 peter
     reference.
     All system catalogs have names  that  begin  with
     <firstterm>pg_</firstterm>.
-    The  following  classes contain information that may be
+    The  following  tables contain information that may be
     useful to the end user.  (There are many  other  system
     catalogs,  but there should rarely be a reason to query
     them directly.)
@@ -141,11 +141,11 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.8 2000/12/26 00:10:37 peter
        </row>
        <row>
 	<entry>pg_class</entry>
-	<entry> classes</entry>
+	<entry> tables</entry>
        </row>
        <row>
 	<entry>pg_attribute</entry>
-	<entry> class attributes</entry>
+	<entry> table columns</entry>
        </row>
        <row>
 	<entry>pg_index</entry>
@@ -195,10 +195,10 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.8 2000/12/26 00:10:37 peter
     </figure>
 
     The Reference Manual gives a more detailed  explanation
-    of  these catalogs and their attributes.  However,
+    of  these catalogs and their columns.  However,
     <xref linkend="EXTEND-CATALOGS">
     shows the major entities and their  relationships
-    in  the system catalogs.  (Attributes that do not refer
+    in  the system catalogs.  (Columns that do not refer
     to other entities are not shown unless they are part of
     a primary key.)
     This diagram is more or less incomprehensible until you
@@ -216,13 +216,13 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.8 2000/12/26 00:10:37 peter
        some  of  these  join  queries  (which are often
        three- or four-way joins)  more  understandable,
        because  you  will  be  able  to  see  that  the
-       attributes used in the queries form foreign keys
-       in other classes.
+       columns used in the queries form foreign keys
+       in other tables.
       </para>
      </listitem>
      <listitem>
       <para>
-       Many  different  features  (classes, attributes,
+       Many  different  features  (tables, columns,
        functions,  types,  access  methods,  etc.)  are
        tightly  integrated  in  this  schema.  A simple
        create command may modify many  of  these  catalogs.
@@ -241,15 +241,15 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.8 2000/12/26 00:10:37 peter
        </note>
 
        Nearly  every catalog contains some reference to
-       instances in one or both of these classes.   For
+       rows in one or both of these tables.   For
        example,  <productname>Postgres</productname>  frequently  uses type 
        signatures (e.g.,  of  functions  and  operators)  to
-       identify unique instances of other catalogs.
+       identify unique rows of other catalogs.
       </para>
      </listitem>
      <listitem>
       <para>
-       There are many attributes and relationships that
+       There are many columns and relationships that
        have obvious meanings, but there are many  
        (particularly  those  that  have  to  do with access
        methods) that do not.  The relationships between

doc/src/sgml/indices.sgml

@@ -35,7 +35,7 @@
      <para>
       For a <firstterm>functional index</firstterm>, an index is defined
       on the result of a function applied
-      to one or more attributes of a single class.
+      to one or more columns of a single table.
       This is a single-column index (namely, the function result)
       even if the function uses more than one input field.
       Functional indices can be used to obtain fast access to data

doc/src/sgml/inherit.sgml

@@ -1,14 +1,14 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/inherit.sgml,v 1.12 2001/01/05 06:34:15 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/Attic/inherit.sgml,v 1.13 2001/01/13 23:58:55 petere Exp $
 -->
 
  <chapter id="inherit">
   <title>Inheritance</title>
 
   <para>
-   Let's create two classes. The capitals  class  contains
+   Let's create two tables. The capitals  table  contains
    state  capitals  which  are also cities. Naturally, the
-   capitals class should inherit from cities.
+   capitals table should inherit from cities.
 
 <programlisting>
 CREATE TABLE cities (
@@ -22,17 +22,17 @@ CREATE TABLE capitals (
 ) INHERITS (cities);
 </programlisting>
 
-   In this case, an  instance  of  capitals  <firstterm>inherits</firstterm>  all
+   In this case, a row  of  capitals  <firstterm>inherits</firstterm>  all
    attributes  (name,  population,  and altitude) from its
    parent, cities.  The type  of  the  attribute  name  is
    <type>text</type>,  a  native  <productname>Postgres</productname>  type  for variable length
    ASCII strings.  The type of the attribute population is
    <type>float</type>,  a  native <productname>Postgres</productname> type for double precision
    floating point numbers.  State capitals have  an  extra
    attribute, state, that shows their state.  In <productname>Postgres</productname>,
-   a  class  can inherit from zero or more other classes,
-   and a query can reference either  all  instances  of  a
-   class  or  all  instances  of  a  class plus all of its
+   a  table  can inherit from zero or more other tables,
+   and a query can reference either  all  rows  of  a
+   table  or  all  rows of  a  table plus all of its
    descendants. 
 
    <note>
@@ -90,7 +90,7 @@ SELECT name, altitude
 
   <para>
    Here the <quote>ONLY</quote> before cities indicates that the query should
-   be  run over only cities and not classes below cities in the
+   be  run over only cities and not tables below cities in the
    inheritance hierarchy.  Many of the  commands  that  we
    have  already discussed -- <command>SELECT</command>,
    <command>UPDATE</command> and <command>DELETE</command> --
@@ -99,7 +99,7 @@ SELECT name, altitude
 
   <para>
   In some cases you may wish to know which table a particular tuple
-  originated from. There is a system attribute called
+  originated from. There is a system column called
   <quote>TABLEOID</quote> in each table which can tell you the
   originating table:
 
@@ -153,7 +153,7 @@ SELECT name, altitude
      In previous versions of <productname>Postgres</productname>, the
      default was not to get access to child tables. This was found to
      be error prone and is also in violation of SQL99. Under the old
-     syntax, to get the sub-classes you append "*" to the table name.
+     syntax, to get the sub-tables you append "*" to the table name.
      For example
 <programlisting>
 SELECT * from cities*;

doc/src/sgml/intro.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.12 2000/09/29 20:21:34 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.13 2001/01/13 23:58:55 petere Exp $
 -->
 
  <chapter id="intro">
@@ -44,7 +44,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.12 2000/09/29 20:21:34 peter
     extend the system:
 
     <simplelist>
-     <member>classes</member>
+     <member>tables</member>
      <member>inheritance</member>
      <member>types</member>
      <member>functions</member>

doc/src/sgml/libpq++.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/libpq++.sgml,v 1.22 2000/12/26 00:10:37 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/Attic/libpq++.sgml,v 1.23 2001/01/13 23:58:55 petere Exp $
 -->
 
  <chapter id="libpqplusplus">
@@ -353,7 +353,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/libpq++.sgml,v 1.22 2000/12/26 00:10:
      <listitem>
       <para>
        <function>Tuples</function>
-       Returns the number of tuples (instances) in the query result. 
+       Returns the number of tuples (rows) in the query result. 
        <synopsis>
 	int PgDatabase::Tuples()
        </synopsis>