I am working towards coming up with an approach to this problem. I have a single-user desktop application sitting on top of MSSQL CE. At this point, the application has a 'FileSave' approach. So there can be lots of activity in the application before anything can hit the database.
One ISession The simplest solution is to just use one ISession. This works out nicely with the level one cache provides all the semantics for the queries are work nicely. If I've updated something, the next query sees that something updated, even if it is not yet in the db. But... from what I understand I will then lock myself out of multi-threading, which may become important as the FileSave operation can potentially get larger. 1) Is this approach too limiting, in-appropriate, a problem just waiting to happen? 2nd Level Cache Alternatively, I've thought about more conventional use of ISession and using a 2nd level cache. I've tried this, but no luck so far. My assumption is that it MUST get into 2nd level cache so that other queries can see it. But I don't know how to get the object into the 2nd level cache, and then just how do I get the update objects in the 2nd level cache to post their changes to the database? I KNOW that the FILESAVE thing makes this far more awkward than it needs to be, but that is how the Project Owners view the world at this point. Any comments are much appreciated. Thanks, jeff --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
