I should've mentioned that this is using a Session per request, and
the QueryOver is being called during this request. The updates and
inserts always occur after the QueryOver is used, the behaviour I was
expecting was the stale objects to flush the session first, before
this query is executed against the SQL Server.

The FlushMode is Auto.

On Aug 22, 5:04 pm, "Chris S." <[email protected]> wrote:
> We're using the UoW pattern with an ASP.NET website, and have upgraded
> one site to NH 3.2. I've got a problem with one call that is
> performing a QueryOver on an entity - the SQL select statement from
> the QueryOver is being called before the update statements when an
> object I previously obtained (using a Get() ) has a its property
> changed.
>
> Should we expect to have to manually flush before doing a QueryOver
> statement? Is there some kind of general guidance for it?
>
> Thanks,
> Chris

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

Reply via email to