…chitecture into develop
With the cast to string, it would try to load 15 instead of users/15, Client must prepend type internally if id is a ValueType.
SaveChanges is supposed to be an atomic operation, if we call it on the session when we had multiple entities changed, it will save all the entities. even if there was no transaction.
Removed as of now, as similar functionality can be configured on the DocumentStore using: Conventions.DefaultQueryingConsistency=ConsistencyOptions.MonotonicRead; Using WaitForNonStaleResults is not recommended as that might cause a long wait/timeouts if there are many writes. If we are going to expose anyting we should at least expost the whole customisation, not just a bool. Dont think we need to though.