[eclipselink-users] Legacy database ddl generation with duplicate column

[zaya <his.stone@xxxxxxxxx>]

It seems to be a bug of eclipselink. I'm working on a legacy database. The
mapping of table is like:

[code]
... table definition

@EmbeddedId
    protected ExercisePK key;

... many other columns

@ManyToOne
    @JoinColumns({
 
@JoinColumn(name="FMemberID",referencedColumnName="FMemberID",insertable=false,updatable=false),
  @JoinColumn(name="FcorpID", referencedColumnName="FCorpID",
insertable=false, updatable=false)
    })
    private AppMember appMember;


[/code]

The problem here is that the composite primary key is composed of the table
auto id and also the "FcorpID" column. Because FcorpID is a global
identifier which exits in every table to distingush similar data from other
corporations.

The mapping itself works fine. But when I want to test database using in
memory db and generate ddl, eclipselink throw exception that it said the
column definition "FcorpID" is duplicated and table is not created.

I'm wondering if this is a bug or there's some configuration I can use to
let eclipselink know that only one column here is needed like when
persisting I turn off insertable and updatable to disable the second
column's modification. Or is this a missing feature?
-- 
View this message in context: http://old.nabble.com/Legacy-database-ddl-generation-with-duplicate-column-definition.-tp27662400p27662400.html
Sent from the EclipseLink - Users mailing list archive at Nabble.com.