Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Are you certain that this is the case? If you're only verifying the isolation level by what NHProf is telling you; that could be a problem. Remember that NHProf is only reporting what the logging infrastructure in NHibernate feeds it. Perhaps the isolation level message isn't sent when you open a transaction with the default? This could probably be verified by investigating the NHibernate source.</p> <p>I would suggest using an alternate means to verify the transaction level (perhaps SQL Profiler?) before concluding that this isn't working as expected.</p> <p><strong>Edit:</strong></p> <p>I've had a look at the NHibernate source and can verify my hunch above. If you have a look at the <a href="http://nhibernate.svn.sourceforge.net/viewvc/nhibernate/tags/2.1.1GA/nhibernate/src/NHibernate/Transaction/AdoTransaction.cs?revision=4816&amp;view=markup" rel="noreferrer">AdoTransaction</a> source you'll note that it is logging an isolation level of IsolationLevel.Unspecified when a transaction is started without specifying a specific isolation level. </p> <pre><code>// This is the default overload you're calling: public void Begin() { Begin(IsolationLevel.Unspecified); } // This is the full method impl public void Begin(IsolationLevel isolationLevel) { // snip.... // This is the problematic line here; it will report an isolationLevel of Unspecified. log.Debug(string.Format("Begin ({0})", isolationLevel)); // snip... } </code></pre> <p>However, the actual transaction is being started with the isolation level specified in the config a few lines down as such:</p> <pre><code>if (isolationLevel == IsolationLevel.Unspecified) { isolationLevel = session.Factory.Settings.IsolationLevel; } </code></pre> <p>So, it would seem that NHProf is not being entirely accurate in this instance.</p> <p><strong>Update:</strong></p> <p>It appears this has been fixed in the trunk version of NHibernate, so I'm guessing this is no longer an issue with NHibernate 3.xx.</p>
    singulars
    1. This table or related slice is empty.
    1. POCannot set a default Nhibernate isolation level (eg via mapping)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDanP
    1. USDanP
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCannot set a default Nhibernate isolation level (eg via mapping)
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAwesome answer! Thank you!
      singulars
      1. PO
      1. USAlistair
    2. CO@Alistair: I mentioned this in the nhprof group as well, but I'm guessing nothing can/will be done about this for NH 2.x users anyways... http://groups.google.com/group/nhprof/browse_thread/thread/b8ceb8f8c1cdb4d3
      singulars
      1. PO
      1. USDanP
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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