+1
On Nov 10, 2009, at 6:25 PM, Bilgin Ibryam wrote:
> Hi all,
>
> I have a question regarding AgreementWorkEffortAppl entity.
> I need to assign WorkEfforts to an Agreement instead of separate
> Agreement Items, but current data model doesn't allow that.
> The reason is in the relations of AgreementWorkEffortAppl entity:
>
> <relation type="one-nofk" rel-entity-name="Agreement">
> <key-map field-name="agreementId"/>
> </relation>
> <relation type="one" fk-name="AGRMNT_WEA_AITM" rel-entity-
> name="AgreementItem">
> <key-map field-name="agreementId"/>
> <key-map field-name="agreementItemSeqId"/>
> </relation>
>
>
> In my opinion the relation to Agreement entity should be "one" but
> not "one-nofk" and the relation to AgreementItem should be "one-
> nofk" instead of "one". This change would allow adding workefforts
> to the agreement w/o specifying an AgrementItem.
>
> Do you think that this change is right and acceptable in the
> project? (together with a service for data migration...)
>
> Bilgin Ibryam
>
Locked
