[
https://issues.apache.org/jira/browse/CAY-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15529779#comment-15529779
]
Andrus Adamchik edited comment on CAY-2113 at 9/28/16 2:35 PM:
---------------------------------------------------------------
Bug #2 .. perhaps warrants a separate Jira:
In the existing "synchronizeWithObjEntity":
protected void synchronizeWithObjEntity(DbEntity entity) {
for (ObjEntity objEntity : entity.mappedObjEntities()) {
new
EntityMergeSupport(objEntity.getDataMap()).synchronizeWithDbEntity(objEntity);
}
}
We are not using EntityMergeSupport from DbImportConfiguration preconfigured
with proper settings for "meaningfulPK" and "usePrimitives". So these reverse
engineering rules are very likely ignored.
was (Author: andrus):
Bug #2 .. perhaps warrants a separate Jira:
In the existing "synchronizeWithObjEntity":
protected void synchronizeWithObjEntity(DbEntity entity) {
for (ObjEntity objEntity : entity.mappedObjEntities()) {
new
EntityMergeSupport(objEntity.getDataMap()).synchronizeWithDbEntity(objEntity);
}
}
We are not using preconfigured EntityMergeSupport with proper settings for
"meaningfulPK" and "usePrimitives". So these reverse engineering rules are very
likely ignored.
> cdbimport: Reverse-engineering reinstates previously ignored columns
> --------------------------------------------------------------------
>
> Key: CAY-2113
> URL: https://issues.apache.org/jira/browse/CAY-2113
> Project: Cayenne
> Issue Type: Bug
> Affects Versions: 4.0.M3
> Reporter: Andrus Adamchik
> Assignee: Andrus Adamchik
>
> Say we have a model:
> {noformat}
> T1:
> ID
> C1
> C2
> O1 -> T1
> c1 -> T1.C1
> {noformat}
> I.e. our ObjEntity intentionally does not map certain columns. Now we add a
> column T1.C3 and rerun cdbimport. The end result is 2 new attributes: c2 and
> c3. Expected - just c3. Removal of "c2" was an earlier user decision and we
> should not recreate it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
