SQLServer, IDENTITY and History issuehttps://www.eclipse.org/forums/index.php/mv/msg/240025/725227/#msg_725227
I am using MS SQL Server 2008 which is automatically detected by EclipseLink on start up. What I am trying to do is to use a history customiser to maintain the log of a table which has an auto-increment identity column as the primary key. The definition of the table and its corresponding history table:

At the bold line the value of the "object" parameter has the field which holds the identity value correctly set to a valid identifier from the database, yet it still decides that it needs to ask the database again for the identifier which I assume is what is failing.

The issue is that EclipseLink thinks the history table is also using identity.

Please vote for the bug.

You should be able to use TABLE sequencing as a workaround (I would recommend TABLE sequencing anyway, as IDENTITY sequencing is very limited in that it does not allow preallocation, so is very inefficient).
]]>James Sutherland2011-09-15T15:43:00-00:00