I am using session.save() method to insert data.

I noticed that hibernate first call an insert statement and then an update statement for each save() call. I am not sure why hibernate is making an update call to database.

[b]My question is can i disable this update call and just have an insert call to database. I feel this update is reducing my application performance. I have around 50,000 rows to be inserted everyday.[/b]

I think that you should call "save" only after setting all the attributes of the object then only an "insert" should be generated. If you modify any attributes of the object after "save" in the same transaction you will get an "insert" followed by an "update".

I am new to Hibernate, but I think this is the "normal" behavior.

I am not making any change to the object. In fact i inserted some System.out in my code just before the call to save() method and just after it.

And in between i saw two calls to DB one is insert and then an update. even though i am not making any chnage to my object

I am not making any change to the object. In fact i inserted some System.out in my code just before the call to save() method and just after it.

And in between i saw two calls to DB one is insert and then an update. even though i am not making any chnage to my object

Ok,

I got the problem. You were right. The object state is being changed. I have a column name update_date in the table. In object instance i pass "new Date()" in the "get" method.

Now this actually changes when the data is being commited to the DB. So it first make an insert to the DB and then makes an update to update the chnaged value of update_date which would change because of some micro seconds difference.

But then how do i insert an update_date to my column which would be current date without this update being called. I am not really bothered about the exact time being inserted.

look at the <timestamp> mapping in hibernate if this is a timeLastUpdated type of attribute.