Hi List :-),
Armin Landscheidt, a friend of mine told me, that it could be a
problem of flushing the session. Usually in a productive environment
you would use transaction to save an object, but I didn't do that for
that simple example. A flush() occurs on calling ISession.Flush()
explicitly and when a Transaction is committed. so the fix is:
using (ITransaction transaction = session.BeginTransaction()) {
session.SaveOrUpdate(i);
transaction.Commit();
}
His very interesting blog is at
http://arminlandscheidtsblog.blogspot.com/ (unfortunately only
German).
Bye,
Patrick
--
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/nhusers?hl=en.
