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 -N -r1.6 -r1.6.2.1
--- openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.adp 25 Apr 2018 08:38:27 -0000 1.6
+++ openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.adp 2 Mar 2019 19:30:04 -0000 1.6.2.1
@@ -1,5 +1,5 @@
- By Michael Bryzek Constraint naming standard is important for one reason: The
@@ -19,8 +22,8 @@
associate a particular constraint with our data model. This gives
us two real advantages: We can quickly identify and fix any errors. We can reliability modify or drop constraints
-Why do we need a naming convention?Oracle limits names, in general, to 30
+
+Oracle limits names, in general, to 30
characters, which is hardly enough for a human readable constraint
name. 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. About Naming the not null
-constraints Though naming "not null" constraints doesn't help
+a requirement. 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. ($Id: constraint-naming.xml,v 1.10
-2018/03/24 00:14:57 hectorr Exp $)