Index: openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.adp,v
diff -u -r1.1.2.5 -r1.1.2.6
--- openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.adp	21 Jun 2016 07:44:36 -0000	1.1.2.5
+++ openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.adp	23 Jun 2016 08:32:45 -0000	1.1.2.6
@@ -57,11 +57,11 @@
 <div class="titlepage"><div><div><h3 class="title">
 <a name="eng-standards-constraint-naming-format" id="eng-standards-constraint-naming-format"></a>Format of
 constraint name</h3></div></div></div><p>&lt;table name&gt;_&lt;column_name&gt;_&lt;constraint
-abbreviation&gt;</p><p>In reality, this won't be possible because of the character
+abbreviation&gt;</p><p>In reality, this won&#39;t be possible because of the character
 limitation on names inside oracle. When the name is too long, we
 will follow these two steps in order:</p><div class="orderedlist"><ol class="orderedlist" type="1">
-<li class="listitem"><p>Abbreviate the table name with the table's initials (e.g. users
--&gt; u and users_contact -&gt; uc).</p></li><li class="listitem"><p>Truncate the column name until it fits.</p></li>
+<li class="listitem"><p>Abbreviate the table name with the table&#39;s initials (e.g.
+users -&gt; u and users_contact -&gt; uc).</p></li><li class="listitem"><p>Truncate the column name until it fits.</p></li>
 </ol></div><p>If the constraint name is still too long, you should consider
 rewriting your entire data model :)</p><p><span class="strong"><strong>Notes:</strong></span></p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
 <li class="listitem"><p>If you have to abbreviate the table name for one of the
@@ -97,9 +97,9 @@
 </pre>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="eng-standards-constraint-naming-pk" id="eng-standards-constraint-naming-pk"></a>Why it's good to name
+<a name="eng-standards-constraint-naming-pk" id="eng-standards-constraint-naming-pk"></a>Why it&#39;s good to name
 primary keys</h3></div></div></div><p>Naming primary keys might not have any obvious advantages.
-However, here's an example where naming the primary key really
+However, here&#39;s an example where naming the primary key really
 helps (and this is by no means a rare case!</p><pre class="programlisting">
 SQL&gt; set autotrace traceonly explain;
 
@@ -114,19 +114,21 @@
    2    1     TABLE ACCESS (FULL) OF 'CONSTRAINT_NAMING_EXAMPLE'
    3    1     INDEX (UNIQUE SCAN) OF 'EXAMPLE_TOPICS_TOPIC_ID_PK' (UNI
           QUE)
-</pre><p>Isn't it nice to see "EXAMPLE_TOPICS_TOPIC_ID_PK" in the trace
-and know exactly which table oracle is using at each step?</p>
+</pre><p>Isn&#39;t it nice to see "EXAMPLE_TOPICS_TOPIC_ID_PK"
+in the trace and know exactly which table oracle is using at each
+step?</p>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
 <a name="eng-standards-constraint-naming-nn" id="eng-standards-constraint-naming-nn"></a>Naming not null
 constraints is optional...</h3></div></div></div><p>People disagree on whether or not we should be naming not null
 constraints. So, if you want to name them, please do so and follow
 the above naming standard. But, naming not null constraints is not
-a requirement.</p><div>About Naming the not null constraints</div><p>Though naming "not null" constraints doesn't help immeditately
-in error debugging (e.g. the error will say something like "Cannot
-insert null value into column"), we recommend naming not null
-constraints to be consistent in our naming of all constraints.</p><div class="cvstag">($&zwnj;Id: constraint-naming.xml,v 1.6 2006/07/17
-05:38:37 torbenb Exp $)</div>
+a requirement.</p><div>About Naming the not null constraints</div><p>Though naming "not null" constraints doesn&#39;t help
+immeditately in error debugging (e.g. the error will say something
+like "Cannot insert null value into column"), we
+recommend naming not null constraints to be consistent in our
+naming of all constraints.</p><div class="cvstag">($&zwnj;Id: eng-standards-constraint-naming.html,v
+1.48.2.10 2016/06/21 07:44:36 gustafn Exp $)</div>
 </div>
 </div>
 <include src="/packages/acs-core-docs/lib/navfooter"