cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrus Adamchik (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAY-2133) ObjectNameGenerator refactoring - unifying relationship name generation
Date Fri, 04 Nov 2016 13:54:58 GMT

     [ https://issues.apache.org/jira/browse/CAY-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrus Adamchik updated CAY-2133:
---------------------------------
    Description: 
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. 

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.

  was:
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. 

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.


> 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
>
> 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. 
> 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)

Mime
View raw message