You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Jason]: ... I found myself needing the foreign key field on all the associations. Can I make a suggestion that the designer set the Foreign Key Property to [TargetEntity]Id by default unless user overrides?
[Michael]: I'm not a big fan of foreign key generation for the entities. They're really not an organic part of the model, and are only there to support the persistence mechanism. It's entirely possible to have a storage mechanism where they're not only not needed, but not possible, so that kind of change goes against the spirit of the extension. That being said, I can see adding the ability to globally add them on command; say, with a context menu command on the designer surface.
The text was updated successfully, but these errors were encountered:
msawczyn
changed the title
Add ability to globally add exposed foreign key properties to entities
Add ability to globally add and remove exposed foreign key properties to entities
Oct 16, 2020
msawczyn
changed the title
Add ability to globally add and remove exposed foreign key properties to entities
Add ability to globally remove exposed foreign key properties to entities
Dec 15, 2020
msawczyn
changed the title
Add ability to globally remove exposed foreign key properties to entities
Add ability to globally add and remove exposed foreign key properties to entities
Aug 14, 2022
From the marketplace:
[Jason]: ... I found myself needing the foreign key field on all the associations. Can I make a suggestion that the designer set the Foreign Key Property to [TargetEntity]Id by default unless user overrides?
[Michael]: I'm not a big fan of foreign key generation for the entities. They're really not an organic part of the model, and are only there to support the persistence mechanism. It's entirely possible to have a storage mechanism where they're not only not needed, but not possible, so that kind of change goes against the spirit of the extension. That being said, I can see adding the ability to globally add them on command; say, with a context menu command on the designer surface.
The text was updated successfully, but these errors were encountered: