Frédéric Delaporte
Frédéric Delaporte
People needing to use older NHibernate should just use the previous cache package version. NuGet allows this. The drawback is for supplying new features to them along to the latest...
I do not see how should this be a concern NHibernate.AspNet.Identity. Can you elaborate? Explain what it may cause for NHibernate.AspNet.Identity features and why should it by handled by it...
A proper fix for this case could be to use something like Criteria/QueryOver `InsensitiveLike`, which Linq/Hql currently lacks. Using `ToUpper` or `ToLower` for emulating case insensitive comparisons is anyway a...
Thanks, May you add a test demonstrating in which cases it makes a difference?
Not the entity, but its identifiers could, as the query cache caches identifiers only, regardless of entity cacheability.
> A working feature might be to only allow queries to be cached if all included queryspaces/persisters have caching enabled. I do not agree. Query caching is enabled on a...
> So, with the latest iteration of changes this has become a close resemblance of "Future" feature, right? > The last iteration of changes applied the same logic in terms...
This sometimes happens, and usually pushing new commit solves it. As anyway you have a conflict to resolve and new issues in CodeFactor, you have some commits to add (eventually...
After having undone the fix in this PR, its tests work locally. So I have pushed the undo to check this with the CI.
So the test case alone without any change to NHibernate current master branch succeeds.