Re: [nhusers] Deleted Entity Appears in Query Results

The FlushMode has three (sensible) options:

Never:  The developer flushes themselves;
Commit:  Flush will only occur at transaction commit;
Auto:  NH will flush as required.

I believe when you are in a transaction, and use FlushMode.Auto (the default), 
each query will examine the tables it uses, and if that intersects with any of 
the tables used in the pending unit-of-work, it will issue a flush first.

I would expect the query in Tim’s example to cause an automatic flush if the 
FlushMode is Auto and inside an NH transaction (notwithstanding we haven’t seen 
the code or mappings).


From: Jason Meckley 
Sent: Saturday, July 30, 2011 2:40 PM
To: [EMAIL PROTECTED] 
Subject: Re: [nhusers] Deleted Entity Appears in Query Results
flushing only occurs after the transaction is committed, not when you call 
save/delete. these types of methods only add commands to the queue. when the 
session is flushed the commands are executed.
-- 
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/nhusers/-/uRspTHNg5XoJ.
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.

-- 
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.