Ahh okay that explains it, I assumed the query would use the cache from the session passed into the Linq extension method. I am still trying to grasp how the Linq provider works.
Thanks for your persistence and your prompt replies! On Mar 23, 5:57 pm, Ayende Rahien <[email protected]> wrote: > Because queries do not look at the session cache > > On Mon, Mar 23, 2009 at 12:58 PM, James Allen < > > > > [email protected]> wrote: > > Sorry, I’m not making myself clear. I understand that UoW has a FlushMode > > of commit. The bit that I don’t understand is **why do I need to flush**. > > It looks to me that Rhino UoW uses the same session as Rhino Repository, so > > should be able to ‘see’ unsaved / unflushed / uncommitted entities in the > > session cache. Obviously I am wrong (because the behaviour does not reflect > > this) but I am trying to understand why I am wrong – I suspect that > > Respository<T>.Save and UnitOfWork.Current.Linq are in fact using entirely > > different sessions? > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" 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/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
