Index: openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.html,v diff -u -r1.39 -r1.40 --- openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.html 16 Feb 2005 00:21:02 -0000 1.39 +++ openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.html 4 Jun 2006 00:45:24 -0000 1.40 @@ -1,4 +1,5 @@ -Constraint naming standard
Alex logo
Prev Chapter�12.�Engineering Standards Next

Constraint naming standard

By Michael Bryzek

+ +Constraint naming standard
Alex logo
Prev Chapter�12.�Engineering Standards Next

Constraint naming standard

By Michael Bryzek

OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff.

The Big Picture

@@ -70,7 +71,7 @@ 3 1 INDEX (UNIQUE SCAN) OF 'EXAMPLE_TOPICS_TOPIC_ID_PK' (UNI QUE)

-Isn't it nice to see "EXAMPLE_TOPICS_TOPIC_ID_PK" in the trace +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?

Naming not null constraints is optional...

People disagree on whether or not we should be naming not null @@ -80,8 +81,8 @@

About Naming the not null constraints

-Though naming "not null" constraints doesn't help immeditately in error +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 +"Cannot insert null value into column"), we recommend naming not null constraints to be consistent in our naming of all constraints.

($Id$)
Prev Home Next
Release Version Numbering Up ACS File Naming and Formatting Standards
docs@openacs.org
View comments on this page at openacs.org