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.1.2.9 -r1.1.2.10 --- openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.adp 6 Jan 2017 09:18:41 -0000 1.1.2.9 +++ openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.adp 16 Jun 2017 17:19:50 -0000 1.1.2.10 @@ -23,16 +23,15 @@ us two real advantages:

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.

Abbreviations

We propose the following naming convention for all constraints, -with the following abbreviations taken from Oracle Docs at -http://oradoc.photo.net/ora81/DOC/server.815/a67779/ch4e.htm#8953. -Note that we shortened all of the constraint abbrevations to two -characters to save room.

+with the following abbreviations taken from Oracle Docs. Note that +we shortened all of the constraint abbrevations to two characters +to save room.