Enforcing use of class word as naming standard via data modeler preferences
819559Nov 29 2010 — edited Nov 30 2010Using data model preferences, I have set both the "attribute" and "column" naming standards to have mandatory name parts of both "prime word" and "class word". I have also used data model preferences to specify a glossary that has several terms of type "class word" defined.
My assumption is that if I set a column naming standard preference to have class word as a mandatory name part, then I can apply the default design rules in my relational model and it will list an error "column with wrong naming standards" if any of my column names don't have a name part that is on the list of class words in the specified glossary. Is that assumption correct? If so, it doesn't seem to be working for me...
How does SDDM determine if a class word is missing? I.e., how can I enforce a naming standard that all attribute/column names must have a class word from our approved list of class words?
Thanks!