[ https://issues.apache.org/jira/browse/ISIS-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood updated ISIS-215: ----------------------------- Fix Version/s: (was: isis-1.0.0) isis-objectstore-sql-1.0.0 > Change way that SQL objectstore determines the properties of an object to be > persisted > -------------------------------------------------------------------------------------- > > Key: ISIS-215 > URL: https://issues.apache.org/jira/browse/ISIS-215 > Project: Isis > Issue Type: Improvement > Components: Objectstore: SQL > Affects Versions: 0.2.0-incubating > Reporter: Dan Haywood > Assignee: Dan Haywood > Priority: Minor > Fix For: isis-objectstore-sql-1.0.0 > > > Noticed that in some circumstances the database table that SQL object store > attempts to create had duplicate column names. Tracked this behaviour down > to the logic within > org.apache.isis.runtimes.dflt.objectstores.sql.auto.AbstractAutoMapper - the > setUpFieldMappers() method can be called into recursively, meaning that the > simple aggregation of columns into a list (as then used by the > setUpFullMapping method is not sufficient). > Although I don't understand everything that is going on here, it seems that a > safer way to proceed is to use a Map and to key the elements by the > ObjectAssociation (ie property); that way there can only ever be one "thing" > added per processed field. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira