Hello,

I've just discovered that SaveOrUpdate doesn't behave consistently for oracle & sqlserver.

In sqlserver new instances are actually inserted into the table before the transaction is committed in order to generate an identity value (on the primary key).

This means that I can run raw sql against the row as long as the sql runs in the same transaction as the insert.

In oracle new instances are not inserted. Instead I only see a select against the sequence.

This means that I cannot run raw sql against the row (since it is not there yet).

Is there a way around this? I mean is there a way I can make the nhibernate on oracle to behave like nhibernate on sqlserver?

Thanks.

Hi,

We've had the same problem, and were able to solve it by adding a Flush() right after the SaveOrUpdate(). This will send the actual SQL statements to the server thus making the rows 'available'.
Use a transaction around all this to ensure that all changes are committed (or rolled back) consistently.

Yup, I do the same thing with Oracle.