Considerations for Hibernate optimistic lock Timestamp

Lt; timestampnameupdDatecolumnUPD_DATEgt; lt; timestampgt; the time for using the AP server after the id is defined, instead

Lt; timestamp name = updDate column = UPD_DATEgt; lt;/timestampgt; the time for using the AP server after the id is defined, instead

This must be after the id Definition

This uses the Time of the AP server instead of the time of the DB server to update the database.

That is, when updating the database, new Date () is used instead of sysdate.

If you want to use the DB server time to update the database, you must add source = "DB"

At this time, hibernate will first extract the current time (select sysdate from dual) from the database, and then use this time for updates.

Instead of using sysdate to update the database strictly (update table1 set upd_date = sysdate ......).

If the UPDATE results do not contain millisecond information, check Dialect and use org. hibernate. dialect. Oracle10gDialect. (Oracle9 and later versions should support milliseconds)

Do not use org. hibernate. dialect. OracleDialect. This class has been Deprecated.

After org. hibernate. dialect. Oracle10gDialect is used, the SQL statement for obtaining the DB Time will change to select policimestamp from dual.

Hibernate Chinese manual PDF

Hibernate details: click here
Hibernate: click here