Can EclipseLink 2.5.2 JPA Use Identity Columns With Oracle12c Database?
(Doc ID 2042718.1)
Last updated on JUNE 03, 2023
Applies to:
Oracle TopLink - Version 12.1.3.0.0 to 12.2.1.2.0 [Release 12c]Information in this document applies to any platform.
Symptoms
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 12.1.3.0.0 EclipseLink 2.5.2 WLS 12.1.3.0.0
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |