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.22 -r1.23 --- openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.html 11 Nov 2003 12:54:57 -0000 1.22 +++ openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.html 19 Nov 2003 15:44:50 -0000 1.23 @@ -1,7 +1,7 @@ -Constraint naming standard
Prev Chapter�9.�Engineering Standards Next

Constraint naming standard

By mbryzek@arsdigita.com


+Constraint naming standard
Alex logo
Prev Chapter�9.�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

+

The Big Picture

Constraint naming standard is important for one reason: The SYS_* name oracle assigns to unnamed constraints is not very understandable. By correctly naming all contraints, we can quickly associate a particular constraint @@ -73,7 +73,10 @@ 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...

-ArsDigita is split 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 at ArsDigita. +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