Can EclipseLink 2.5.2 JPA Use Identity Columns With Oracle12c Database?
(Doc ID 2042718.1)
Last updated on AUGUST 28, 2020
Applies to:Oracle TopLink - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 12c]
Information in this document applies to any platform.
An EclipseLink application attempts to use an Oracle Identity column in JPA, but is found incompatible with JPA.
If SQL: insert INTO Projects (department_name) values (“dept1”) is directly executed, the Identity column can work well.
1. Prepare a Projects table to define an Oracle Identity column:
Environment TopLink 126.96.36.199.0 EclipseLink 2.5.2 WLS 188.8.131.52.0
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document