Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COInteresting that adding a transaction works, even if I don't commit after calling SaveOrUpdate. Somehow, adding the transaction changes how NHibernate behaves, which I find a bit strange. However, I am already using TransactionScope (as this is a legacy app), which means that I can't use NHibernate BeginTransaction (at least, I have encountered all types of problems if I do try and use it). However, with a TransactionScope, the Assert fails. Seems like I need a way to make NHibernate behave as if I had called BeginTransaction, but to use the TransactionScope instead.
      singulars
    2. CO@cbp: That's disconcerting. Be careful with using a transaction without making a call to its Commit method. The transaction will be implicitly rolled back. This article: http://forum.springframework.net/showthread.php?t=5351, may help you. It deals with integrating TransactionScope and ITransaction. Incidentally, do you use a profiling tool or inspect the sql log file created by the NHibernate engine? If so, either the save/update query isn't happening when you expect it to or there are issues with NHibernate's first-level caching mechanism. I suspect the former is the case.
      singulars
    3. CO@cbp: I meant to say, if you are looking at the sql log, you can determine exactly when statements are being executed against the database. As you can see, it's not painfully obvious when this actually happens.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload