</listitem>
<listitem>
<para>
- <parameter>:normalisedp</parameter> - specifies whether
- this class uses normalised inheritance from parent classes.
- Defaults to nil, i.e. non-normalised schemas. When true,
+ <parameter>:normalizedp</parameter> - specifies whether
+ this class uses normalized inheritance from parent classes.
+ Defaults to nil, i.e. non-normalized schemas. When true,
SQL database tables that map to this class and parent
classes are joined on their primary keys to get the full
set of database columns for this class.
this class.
</para>
- <title>Normalised inheritance schemas</title>
+ <title>Normalized inheritance schemas</title>
<para>
- Specifying that <symbol>:normalisedp</symbol> is <symbol>T</symbol>
- tells &clsql; to normalise the database schema for inheritance.
+ Specifying that <symbol>:normalizedp</symbol> is <symbol>T</symbol>
+ tells &clsql; to normalize the database schema for inheritance.
What this means is shown in the examples below.
</para>
<para>
- With <symbol>:normalisedp</symbol> equal to <symbol>NIL</symbol>
+ With <symbol>:normalizedp</symbol> equal to <symbol>NIL</symbol>
(the default) the class inheritance would result in the following:
</para>
<screen>
</screen>
<para>
- Using <symbol>:normalisedp</symbol> <symbol>T</symbol>, both
+ Using <symbol>:normalizedp</symbol> <symbol>T</symbol>, both
view-classes need a primary key to join them on:
</para>
<screen>
((user-id :accessor user-id :initarg :user-id
:type integer :db-kind :key :db-constraints (:not-null))
(nick :accessor nick :initarg :nick :type (varchar 64)))
- (:normalisedp t))
+ (:normalizedp t))
SQL table USER:
+---------+-------------+------+-----+---------+-------+
<para>
In this second case, all slots of the view-class 'node
are also available in view-class 'user, and can be used
- as one would expect. For example, with the above normalised
+ as one would expect. For example, with the above normalized
view-classes 'node and 'user, and SQL tracing turned on:
</para>
<screen>