... | ... | @@ -19,7 +19,8 @@ When the time came to be represent the association process, it was decided to us |
|
|
|
|
|
However, the Model Entity Item (in order to be used for modeling associations) behaves differently from all other Items and can cause problems. When you append a model entity to this item it first looks to see if there are any available "slots" in the vector to store it before it tries to append.
|
|
|
|
|
|
To demonstrate this consider 2 items (an int item (I) and a model entity item (M). Lets assume both are of length 4 and they can are extensible. Also assume they have no defaults so all 4 values are unset. If I call append on I, the result is an item of 5 values with the first 4 not set. If I do something similar to M I get an item with 4 values (first value is now set and the remaining 3 are not).
|
|
|
To demonstrate this consider 2 items (an int item (I) and a model entity item (M). Lets assume both are of length 4 and they are extensible. Also assume they have no defaults so all 4 values are unset. If I call append on I, the result is an item of 5 values with the first 4 not set. If I do something similar to M, I get an item with 4 values (first value is now set and the remaining 3 are not).
|
|
|
|
|
|
In order to model the set behavior requirement for associations, the item's behavior has to differ in another important aspect - it can't insert the same model entity more than once!
|
|
|
|
|
|
## Proposed Solution
|
... | ... | |