Hello,

Should save or merge generate an insert statement if the session is not flushed?

I realise that it would have to if you were using a sql server identity column (because it needs to go straight to the database to get it), but I thought it wouldn't if you were using a different type of primary key such as a UUID?

cheers,
Jordan.

Anyone know this? I can't find info in any docs.

My understanding is that SQL should be generated when the session is flushed. (Either explicitly by calling session.flush(), or when a transaction commits and the flush mode is set to 'Commit' or 'Auto').

Is this true? Or would save/merge cause SQL to be generated immediately?

cheers,
Jordan.

Hi Jordan,
A flush causes the sql statements to be prepared. And these get executed at the transaction commit time.
So, in case where flush() is manually invoked after a save()/update(), the sql gets generated at that time itself and they get executed at tx commit time.
However if a flush() is not manually called, the sql gets both generated and executed at the tx commit time itself(Happens only if the flush mode is auto or commit).
The only scenario where the sql does not get generated and save()/update() will not work will be if flush mode is specified as Manual and the flush() is not invoked manually.

Hope this helps,

Hi,

Yes - what you have written is exactly what I would expect.

However, this is not the behaviour I am seeing in a .NET Nhibernate application. I am seeing SQL generated when I call merge despite the fact the the flush mode is set the 'NEVER' and flush is not invoked manually. I have not had time to test how java hibernate behaves - that is why I thought I would ask here first. When I get time I'll write a test.

regards,
Jordan