Eclipse Community Forums: EclipseLink » Problems migrating from eclipselink 2.7.8 to 2.7.9

Home » Eclipse Projects » EclipseLink » Problems migrating from eclipselink 2.7.8 to 2.7.9(Problems with session customizers)

Show: Today's Messages :: Show Polls :: Message Navigator

Problems migrating from eclipselink 2.7.8 to 2.7.9 [message #1847975]

Mon, 15 November 2021 21:32

Dave Brosius

Messages: 34
Registered: July 2009

Member

Hi folks we've had code running on various versions of eclipse link up thru 2.7.8 that worked fine for using session customizers to inject fields as part of transactions. In 2.7.9 something seems to have broken. Was there any changes around this area that i can look into?

We do (roughly):

ReturningPolicy rp = new ReturningPolicy();
rp.addFieldForInsertReturnOnly(table + "." + JPAEntityUtils.getPhysicalColumnName(doClz, Updateable.CREATE_DATE), Date.class);
rp.addFieldForInsertReturnOnly(table + "." + JPAEntityUtils.getPhysicalColumnName(doClz, Updateable.UPDATE_DATE), Date.class);
rp.addFieldForUpdate(table + "." + JPAEntityUtils.getPhysicalColumnName(doClz, Updateable.UPDATE_DATE), Date.class);

descriptor.setReturningPolicy(rp);

where we do:

create or replace trigger %{TRIGGER_NAME}
before insert or update
on %{BASE_TABLE_NAME}
FOR EACH ROW
BEGIN
:NEW.%{UPDATE_TS_COLUMN} := %{SYSDATE_REFERENCE};
IF INSERTING THEN
:NEW.%{CREATE_TS_COLUMN} := %{SYSDATE_REFERENCE};
END IF;
end;

The issue is, now, when update happens, we clear out the create date column. Setting of the create date should only happen on the create, not update. If we roll back to 2.7.8 it works as it should.

Report message to a moderator