Yes, it is expected. Use Flushmode.Commit or call session.flush manually.
/g — Sent from Mailbox On Wed, Feb 4, 2015 at 9:45 PM, sturdytree <[email protected]> wrote: > If I have the following, with a FlushMode of Never: > using (ITransaction txn = Session.BeginTransaction) > { > Session.Delete(entity); > txn.Commit > } > is it expected behaviour that subsequently calling Session.Query<T> to load > all entities will include the above entity, where Flush is called after > Session.Query? > The reason I call Flush later is that I run Session on a separate thread so > database calls take place behind the scenses and don't slow the application. > -- > 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 > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/nhusers. > For more options, visit https://groups.google.com/d/optout. -- 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 email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout.
