cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dzmitry Kazimirchyk (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CAY-1606) Change CayenneModeler new object naming strategy
Date Fri, 02 Sep 2011 12:14:09 GMT

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

Dzmitry Kazimirchyk closed CAY-1606.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 3.1M3
         Assignee: Dzmitry Kazimirchyk

Changed naming to following:
domain -> "project"
DataNode -> "datanode", "datanode1", etc.
DataMap -> "datamap", "datamap1", etc.
DbEntity -> "db_entity", "db_entity1", etc.
ObjEntity -> "ObjEntity", "ObjEntity1", etc.
Embeddable -> "Embeddable", "Embeddable1", etc.
Procedure -> "procedure", "procedure1", etc.
Query -> "query", "query1", etc.

> Change CayenneModeler new object naming strategy
> ------------------------------------------------
>
>                 Key: CAY-1606
>                 URL: https://issues.apache.org/jira/browse/CAY-1606
>             Project: Cayenne
>          Issue Type: Improvement
>    Affects Versions: 3.1M2
>            Reporter: Andrus Adamchik
>            Assignee: Dzmitry Kazimirchyk
>             Fix For: 3.1M3
>
>
> Default modeler object naming (UntitledDomain, UntiltledDomainMap) trickles to the XML
file naming, resulting in mixed case names that look rather ugly. A suggested new naming strategy
is the following:
> * "project" for domains (there can be only 1 per project in 3.1), 
> * "datamap", "datamap1", etc. for DataMaps.
> * "datanode", "datanode1", "datanode2", etc. for DataNodes
> * "dbentity", "dbentity1", etc. for DbEntities
> * "objentity", "objentity1", etc. for ObjEntities
> * Same for procedures, queries and embeddables.
> These will result in cleaner file names like cayenne-project.xml, datamap.map.xml etc.
> Also IIRC the same strategy is used in places outside the Modeler (cdbimport?) so we'll
need to check what gets affected by this change, and whether we can place the strategy in
a corresponding DI module (not the main ServerModule)??

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message