Non Null BLOB is not Inserted Through Triggers When Using Java Persistence API
(Doc ID 1927700.1)
Last updated on MARCH 22, 2019
Applies to:Oracle TopLink - Version 22.214.171.124.1 and later
Information in this document applies to any platform.
A table (Employee ) is created in Oracle Database that contains a BLOB type column (lobData).
A trigger is defined on this table (Employee ) so
that for any insert / update on a row , a copy of the inserted / updated row
is done to another similar table (Employee_copy) with
a blob column (lobData).
An entity is mapping the table Employee :
The problem occurs when persisting Employee entity with a non null BLOB :
the corresponding row is well inserted into Employee table
with a non null blob column (lobData).
But the row inserted into the Employee_copy table thanks to the trigger
has the corresponding blob column (lobData) empty.
The expected behavior is that Employee_copy contains a row with a non null blob
value as in Employee.
The used Eclipselink version is 1.0.2 .
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