added repro for RavenDB-2314
added new file to csproj
minor
- Unified Notification names with RavenDB
- Extracted all the connection behavior out to the abstract RemoteChangesClientBase class.
- Introduced the interfaces IChangesConnectionState and IConnectableChanges to handle the inner workings of the RemoteChangesClientBase class.
- Refactored the RemoteDatabaseChanges class in terms of the RemoteChangesClientBase.
- Implemented the RemoteFilesystemChanges class in terms of the RemoteChangesClientBase. * untested yet.
RavenDB-2015 Added quotas settings
RavenDB-2015 Added updating ETag after saving the record
- Implementation of RemoteFilesystemChanges.
* All tests updated and green.
- Removed old implementation of server notifications.
- Core tests ensuring that the proper inheritance change for the RemoteChangeClientBase raises exceptions when not following the pattern.
- Tests names makes more sense for the purpose of showing how to implement a changes client.
- Changed the Notification property to use a .Changes() method to mimic RavenDB.
Merge branch 'unified-changes-api'
- Replicated changes for issue RavenDB-2321 from the 2.5 branch into 3.0 branch and RavenFS.
- Getting rid of the last reference to the NameValueCollectionJsonConverter (which is not used anymore since the RavenJObject metadata).
Merge branch 'RavenDB-2015' of https://github.com/marad/ravendb
- Fixed: RavenDB-2320.
* Added validation on the admin controller that the call is not an update. We require to pass update=true when we are dealing with an update.
* Added new method CreateOrUpdate (old Create behavior) with the update flag on and the new Create will fail with an InvalidOperationException.
* The HTML Studio still does not support to change the file system configuration therefore we just validate with case insensitive behavior.
* http://issues.hibernatingrhinos.com/issue/RavenDB-2320
- Typos
Merge branch 'master' of https://github.com/Corvalius/ravendb
fix for issue RavenDB-2314
Merge branch 'RavenDB-2314' of https://github.com/ReginaBricker/ravendb
Making sure that the error handling during lucene field creation isn't limited to just spatial errors.
All such errors should be caught, including during reduce.
Batch operation should check if cancellation wasnt requested on CTS