[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[ogee-dev] Bug 463954 - Cross referenced IDs of objects cause inconsistencies in projects
|
Hi,
I would like to discuss bug 463954. Here are my thoughts, and I would be happy to get some feedback.
When building tools that refer to the OData model maintained in Ogee from within a separate EMF resource, you might run into the cross referencing issues described in the bug. As described in the text of the ticket, an option to solve the issue would be to introduce keys instead of just using plain ELists. The OData names of the model elements cannot be used as unique keys, as a design time tool is supposed to be able to store even inconsistent models, e.g. an entity type containing properties with duplicate names. So some other keys like UUIDs would be needed, but this again has some implications. In addition it would be nice to completely overcome our proprietary format for the OData models and switch to EDMX. So would it also be feasible to reference OData elements from an Ogee model using names/paths only when referencing them from within a different resource? I know it sounds complicated, but perhaps we can discuss this here.
What do you think?
Regards,
Klaus
