Hi,

I am using hibernate 3.1.3.

In one hibernate session I am creating and updating the same object. I am executing update using createQuery method. I will always update this object using createQuery method. In hibernate mapping file "show_sql" is set to true. So when I execute my program I am seeing one insert and two update sql statements. I am totally confused why hiberate is sending two updates.

Other thing which I have noticed if I create and update of object in two different sessions then hibernate creates only one update statement.

MY PROGRAM
=============
Session session = HibernateSessionFactory.openSession();
Transaction tx = session.beginTransaction();
// insert record
User user = new User();
user.setId(1);
user.setName("test");
user.setDescription("testing create");
session.save(user);
// update same record
Query query = session.createQuery("update User set name=? where id=?");
query.setParameter(0, "newName");
query.setParameter(1, 1);
int numInserted = query.executeUpdate();
tx.commit();
session.close();

OUTPUT SQL
===================
Hibernate: INSERT INTO User (name, description, id) VALUES (?, ?, ?)

Hibernate: UPDATE User SET name=?, description=? WHERE id=?

Hibernate: update User SET name=? WHERE id=?

MAPPING FILE
========================
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">

<hibernate-mapping package="systemdb.model">
<class name="User" table="User">
<id name="id" column="id" type="int">
<generator class="assigned"/>
</id>
<property name="name" column="name" type="string"/>
<property name="description" column="description" type="string"/>
</class>
</hibernate-mapping>

It will be very greatful if somebody can explain me why this is happening. Is there are any configuration I have to set so that hibernate won't generate its own update statement and just use which are specified in createQuery method.

Thanks.

Sanjeev

You want to look at http://www.hibernate.org/hib_docs/v3/re ... tch-direct

Basically, bulk update delete statements should not be issued from sessions which already have entities associated with them.

But anyway, the first update comes from the flush process that occurs prior to executing the HQL query. Somehow the Session thinks that User has changed between the time you save() it and the time it gets flushed. Typically this indicates bad getter/setter implementations or problems with the type mappings. Paste in the source of your User class (and please use the code tags)...

Thanks you.

You were right. My junit test between the insert and update was updating the user object.

Is it possible if you can reply to one of my posting where I am waiting for a correct answer.

http://forum.hibernate.org/viewtopic.php?t=959208

Thanks.