minor bug (or annoyance) with one-sided relation-properties

Discussion of open issues, suggestions and bugs regarding Entity Developer - ORM modeling and code generation tool
Post Reply
mindplay
Posts: 148
Joined: Tue 13 Dec 2011 22:58
Location: Ithaca, NY

minor bug (or annoyance) with one-sided relation-properties

Post by mindplay » Fri 23 Dec 2011 21:19

When you have an Association where End 2 isn't set to "Generate related property", the property-name isn't saved - the name reverts to the default every time you save/load the model.

For that matter, I don't know why the disabled end of a property is displayed on the diagram at all? I know it's grayed out, but if it's disabled, it won't result in any code, schema or mapping anyway, so how is it relevant?

Could we have an option to disable them perhaps?

Shalex
Site Admin
Posts: 8247
Joined: Thu 14 Aug 2008 12:44

Post by Shalex » Tue 27 Dec 2011 18:07

It is greyed out to identify that there is no corresponding property. This is a designed behaviour.

mindplay
Posts: 148
Joined: Tue 13 Dec 2011 22:58
Location: Ithaca, NY

Post by mindplay » Wed 28 Dec 2011 15:07

I realize this is designed behavior, but I don't understand what relevance it has - since the property is not part of my model, why would I need to see it on the model diagram?

In my world, these diagrams serve as documentation as well as for code-generation - for documentation-purposes, I don't like to have non-existent properties displayed on my diagrams, I find it misleading.

I wish you would add an option to hide them - but at least, could you have the names save properly? Currently, I'm ending up with a lot of "Item1, Item2, Item3" properties on my diagrams, which looks really bad.

Shalex
Site Admin
Posts: 8247
Joined: Thu 14 Aug 2008 12:44

Post by Shalex » Thu 29 Dec 2011 09:45

Relation property really exists in the object model but doesn't take part in code generation and serialization. That's why it is displayed on the model diagram.

mindplay
Posts: 148
Joined: Tue 13 Dec 2011 22:58
Location: Ithaca, NY

Post by mindplay » Thu 29 Dec 2011 14:16

Shalex wrote:Relation property really exists in the object model but doesn't take part in code generation and serialization.
No, the relation exists (and is indicated by the association connector) - the relation property does not exist. You're not even saving it's name.

Helen
Devart Team
Posts: 127
Joined: Wed 07 Sep 2011 11:54

Post by Helen » Tue 03 Jan 2012 14:30

This behaviour will be changed starting from the next build:
  • The navigation property will not be displayed on the diagram and in Model Explorer if 'Generate' is set to false for the appropriate association end
We will post here when the corresponding build of Entity Developer is available for download.

Helen
Devart Team
Posts: 127
Joined: Wed 07 Sep 2011 11:54

Post by Helen » Thu 12 Jan 2012 14:56

New version of Entity Developer 4.2.110 is released!
The new build can be downloaded from http://www.devart.com/entitydeveloper/download.html (the trial and free versions) or from Registered Users' Area (provided that you have an active subscription).

For the detailed information about the improvements and fixes available in Entity Developer 4.2.110, please refer to
http://www.devart.com/forums/viewtopic.php?t=23135

mindplay
Posts: 148
Joined: Tue 13 Dec 2011 22:58
Location: Ithaca, NY

Post by mindplay » Mon 16 Jan 2012 19:05

Looks good! Thanks for addressing this! :-)

Post Reply