Here is my java code:

Item item = new Item();
item.setName("Odissea nello spazio");

Session session = HibernateUtil.currentSession();
tx = session.beginTransaction();
session.saveOrUpdate(item);
item.setDescription("libro");
tx.commit();


This code is resolved in one SQL INSERT and one SQL UPDATE, instead i expected only 1 INSERT.
Here is the log of the sql:


[main] Hibernate: insert into ITEMS (name, description) values (?, ?)
[main] Hibernate: update ITEMS set name=?, description=? where item_id=?

Do you think i missed some configuration or approach, or is this what hibernate is expected to do?

Set the description before calling saveOrUpdate?

I would assume that once the item gets into the session then anything you change will be updated during the flush (a la the commit).

For Example

update(item);
item.setName("balh");
item.setDescirption("blah blah");

will produce only 1 update...i don't understand why mixing insert and update then, it will produce 2 sql command.

I don't really have the time to invest trolling through the source code in depth but in 3.0 at least it would appear that inserts/deletes and updates are maintained in separate collections to be processed.

So I would assume that calling save and then updating the object would provide 2 entries, one for the insert and one for the update. It looks like updates used to be kept in a Hash (or so the comment in the SessionImpl says) so that multiple 'updates' would be collected and executed once. Now in 3, it's an ArrayList but I'm not quite sure of all the semantics.

Anyone that has a clue can jump in at any time ;)

mapping files please