Hi,
I'm seeing the following behavior where saving an entity with generated
identity "flushes" previous Saves on new entities but have no identity
column that haven't been commited/flushed yet, but does not do the same
when the previous uncommited Save actions are updates. I didn't find
In fact, you should avoid identity fields when using NHibernate
Em Seg, 17 de out de 2016 20:33, Gunnar Liljas
escreveu:
> A Save on a new entity with an identity POID will flush any pending
> actions. Updating EntityA in Scenario2 doesn't add any pending actions
>
A Save on a new entity with an identity POID will flush any pending
actions. Updating EntityA in Scenario2 doesn't add any pending actions
until the commit is called. In fact, you should not call Save when you're
updating.
/G
2016-10-17 23:14 GMT+02:00 isern regalis :
>
I think that's a bit too categorical. However, you should definitely be
aware of how they behave.
/G
2016-10-18 0:34 GMT+02:00 Paulo Quicoli :
> In fact, you should avoid identity fields when using NHibernate
>
> Em Seg, 17 de out de 2016 20:33, Gunnar Liljas
The error is pretty self explanatory. Your missing the oraops10.dll.
In your project migration did you upgrade the version of NHibernate? If
you did, you could move to the Oracle managed driver which makes all of the
Oracle client issues dissappear.
Integration with the native oracle client
Solved here:
http://stackoverflow.com/questions/16395956/nhibernate-ipostinserteventlistener-insert-executed-multiple-times
--
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To unsubscribe from this group and stop receiving emails from it, send an