[
https://issues.apache.org/jira/browse/CAY-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrus Adamchik closed CAY-2133.
--------------------------------
Resolution: Fixed
Fix Version/s: 4.0.M4
side effect: an issue with naming 1..1 relationships is fixed, where a
relationship on the master side would incorrectly use the name of the
relationship on the dependent side.
> ObjectNameGenerator refactoring - unifying relationship name generation
> -----------------------------------------------------------------------
>
> Key: CAY-2133
> URL: https://issues.apache.org/jira/browse/CAY-2133
> Project: Cayenne
> Issue Type: Improvement
> Reporter: Andrus Adamchik
> Assignee: Andrus Adamchik
> Fix For: 4.0.M4
>
>
> Will need to refactor ObjectNameGenerator API, mainly focusing on
> relationship name generation. The new API will generate both obj and db
> relationship names in a single method. We will no longer distinguish between
> the two, as DbRelationship name does not correspond to any actual name found
> in the database, and we might as well use the object layer name. The main
> visible change in the algorithm is that ObjRelationship name will be based on
> DbRelationship semantics, not on DbRelationship name.
> In the future if this proves to be too limiting, we might split a separate
> DbRelationship name generator. For now it will allow to avoid passing
> ExportedKey object to the strategy, and make it private.
> As a part of this task we will remove LegacyObjectNameGenerator that uses
> different assumptions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
