2.1.4

<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping SYSTEM "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd" >
<hibernate-mapping package="gov.ijob.domain.po.talents">
<class name="TbTestPO" table="TBTEST" schema="ijob">
<id name="testId" column="TEST_ID" type="java.lang.String" >
<generator class="com.dsii.common.hibernate.CustomizedIdGenerator">
<param name="field_name">tbtest_pk</param>
<param name="rule">*yyyyMMdd,#s6</param>
</generator>
</id>

<timestamp name="modifyDate" column="MODIFY_DATE"/>
<property name="contents" column="CONTENTS" type="java.lang.String"/>

</class>
</hibernate-mapping>

Transaction tx=session.beginTransaction();
tbTestPO.setTestId("20050107000000");
tbTestPO.setContents("OOKK");
tbTestPO.setModifyDate(new Timestamp(System.currentTimeMillis()));
session.update(tbTestPO);
tx.commit();

net.sf.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect) for gov.ijob.domain.po.talents.TbTestPO instance with identifier: 20050107000000
at net.sf.hibernate.persister.AbstractEntityPersister.check(AbstractEntityPersister.java:501)
at net.sf.hibernate.persister.EntityPersister.update(EntityPersister.java:672)
at net.sf.hibernate.persister.EntityPersister.update(EntityPersister.java:642)
at net.sf.hibernate.impl.ScheduledUpdate.execute(ScheduledUpdate.java:52)
at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2414)
at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2368)
at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:2236)
at net.sf.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:61)
at gov.ijob.domain.bean.talents.test.ResumeBasicInfoBeanTest.testCreate(ResumeBasicInfoBeanTest.java:89)
at gov.ijob.domain.bean.talents.test.ResumeBasicInfoBeanTest.main(ResumeBasicInfoBeanTest.java:47)

oracle 9.2

update ijob.TBTEST set MODIFY_DATE=?, CONTENTS=? where TEST_ID=? and MODIFY_DATE=?

Debug level Hibernate log excerpt:

is it a bug?if i get rid of timestamp,i can work well

by the looks of your column name (MODIFY_DATE) it looks to me the column only store the DAY (not milliseconds)....that would make it only possible to update a row once a day - probably not what you want ;)

<timestamp> and <version> is for optimistic locking - not to track which day it was update.

thank you very much. MODIFY_mDATE is used for optimistic locking,it stores in milliseconds,not for date, it prevent me updating.if i moved <Timestamp> tag,it can work well.

i have no idea what you just wrote ?