| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
We have an Object CARTRIDGE, which is under NODE (a few levels down) with an attribute SIDES, and a child object, SIDE. MCC cannot seem to deal with this very well. When we try to deal with the side object, MCC complains about setting illegal values for the sides attribute. MCC> SET NODE PLOW BranchLibrary Fred Cartridge AA0001 Side 1 cleans=3 results in a complaint of an illegal value for the attribute SIDES.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4409.1 | please review uniqueness naming rules in SRM | GOSTE::CALLANDER | Wed Jan 20 1993 12:14 | 15 | |
that is correct, if you check the SRM rules for uniqueness naming
of children and attributes, chapter 7 section 4, you will see that
attribute names must be unique within the set of attribute names,
event names, and child class names, for each entity (note this is
not across all entities, but within the context of each
entity/childentity).
For completeness, please note that entity class names must be unique
across entity class names, directives, attributes, events, groups,
partitions and argument names.
The string 'SIDE' is not unique since it is a complete substring
of 'SIDES', therefore it can never be distinguished from SIDES
(the parser can handle only one match when validating a keyword).
| |||||