I see strange behavior of Hibernate, if this is documented somewhere, please give me more or less precise reference on documentation item.

Order of SQL statements is not same as order of invocations. First I remove all User's, then I add new one. But I see insert first and delete only after insert. Why? What if I will delete bean and insert bean with same primary key? I will have exception.



Hibernate version: 3.1

Code between sessionFactory.openSession() and session.close():

Transaction transaction = session.beginTransaction();
try {
Query query = session.createQuery("select u from User as u");
for (Iterator I = query.list().iterator(); I.hasNext();) {
User user = (User) I.next();
System.out.println(user);
session.delete(user);
}
//
User user = new User();
user.setName("New user " + System.currentTimeMillis());
user.setPassword("secret");
session.save(user);
} finally {
transaction.commit();
}


Full stack trace of any exception that occurs:
Hibernate: /* select u from User as u */ select user0_.id as id0_, user0_.name as name0_, user0_.password as password0_ from users user0_
ru.nlmk.test.User@f8395f[m_id=402886a408517e390108517e416b0001,m_name=New user 1135238594903,m_password=secret]
Hibernate: /* insert ru.nlmk.test.User */ insert into users (name, password, id) values (?, ?, ?)
Hibernate: /* delete ru.nlmk.test.User */ delete from users where id=?


Name and version of the database you are using: Oracle 9.2

Yes, it's written in documentation.
Page 99 of hibernate 3.0.2 documentation (probably in 3.0.1 too):


In general i won't recommend the reuse of a primary key inside a session (delete+insert), as an update is more appropriate.

however if you really need to do it, then issue a Session.flush() between the delete and the insert.


damn, coffee is cold[/i]

Thank you, session.flush() helped, this is page 126 in 3.1 documentation.

I just test how to work with Hibernate, so write useless code, like delete/re-insert. This is good that I found such problem during testing and not in real project. :-)

Sorry i read hibernate 3.0.1 as your version instead of 3.1

Anyway, a good project with unittesting would discover this quite easily ;)
but yes you would have to redo a bit of design :p