Hibernate currently provides a way to define custom types. Either internal or user types.
In some situations, this custom type may have to access the entity identifier.
Concrete use case: compute a custom value using the entity identifier (may be null depending on the id strategy which is used).
This is currently possible from the nullSafeGet method through the owner but this is not possible to access that identifier from the nullSafeSet Method.
So, the proposal would be to review the Hibernate internals to allow exposing this identifier as follow on the UserType interface and call this new method instead of the current one
{code:java}public interface UserType {
// hibernate would call this method internally
// id parameter is the owner/entity identifier
default void nullSafeSet(PreparedStatement st, Serializable id, Object value, int index, SharedSessionContractImplementor session) throws HibernateException, SQLException {
nullSafeSet(st, value, index, session);
}
// may have a default implementation to allow choosing to override one or the other
void nullSafeSet(PreparedStatement st, Object value, int index, SharedSessionContractImplementor session) throws HibernateException, SQLException;
}{code}
Usage may be as follow
{noformat}public class MyType implements UserType {
@Override
void nullSafeSet(PreparedStatement st, Serializable id, Object value, int index, SharedSessionContractImplementor session) throws HibernateException, SQLException {
// compute my new type using the owner/entity id
}
@Override
void nullSafeSet(PreparedStatement st, Object value, int index, SharedSessionContractImplementor session) throws HibernateException, SQLException {
// does nothing ... default implementation in the interface?
}
}{noformat}
The Type interface would also need to be updated the same way to allow transmitting the id from the caller stack. See CustomType.
Proposed change is retro-compatible. |
|
