The reason why the date column gets a null
value when inserting, even though it is defined as default SYSDATE
dbms-side, is that the default
value for a column is only used if the column is not given a value in the query. That means it must not appear in the INSERT INTO
sentence, even if it has been given null
.
If you want to use the default SYSDATE
on the DBMS side, you should configure the @Column
with insertable=false
in order to get the column out of your SQL INSERT
s.
@Temporal(TemporalType.TIMESTAMP)
@Column(name = "myDate", insertable=false)
private Date myDate;
Take into account that this approach will always ignore the value you provide to the property in your app when creating the entity. If you really want to be able to provide the date sometimes, maybe you should consider using a DB trigger to set the value instead of a default value.
There's an alternative to using the default SYSDATE
definition of the DBMS. You could use the @PrePersist
and @PreUpdate
annotations to assign the current date to the property, prior to save/update, if and only if it has not been assigned yet:
@PrePersist
protected void onCreate() {
if (myDate == null) { myDate = new Date(); }
}
This closely related question provides different approaches: Creation timestamp and last update timestamp with Hibernate and MySQL.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…