VelocityDB & VelocityGraph

Object and Graph Database - ask us, share & let us know what you need.

VelocityDB Version 6.0 Release Notes

Replaced IRelation interface with IReferenceTracked and ReferencedTracked. Added a simple Relations sample to show example usage of this API. Moved all exception classes to a separate namespace. Add a .Net Standard 1.6 library to Nuget and download (VelocityDBStandard.dll). Updated driver to LinqPad – added a couple of missing references.

VelocityDB Version 5.8 Release Notes

Moved BTree extensions to namespace VelocityDb.Collection.BTree.Extensions.BTreeExtensions. If you are using indexes or doing LINQ queries with BTreeSet, you need to add:

using static VelocityDb.Collection.BTree.Extensions.BTreeExtensions

to your files that does or else index/BTreeSet lookups will be slow. The same extensions are also provided in the VelocityDBExtensions library which is included with source code in the download and now also as a NuGet. To use that code instead of the VelocityDB build in extensions do using static VelocityDBExtensions.Extensions.BTree.BTreeExtensions; instead and you will be able to debug the code and hopefully help us improve this tricky expression tree code.

VelocityDB Version 5.5.1 Release Notes

Enable index fields with IOptimizedPersistable. Some fixes for updated DynamicDictionary test. Fixes for DateTime indexing. LoadFields moved from IOptimizedPersistable to SessionBase to simplify interface.

VelocityDB Version 5.4.5 Release Notes

Add explicit clear of weak reference object cache when clearing potentially out of date objects in a database. Our online issue manager was seen picking up these invalid objects. With this change, this issue is gone.

VelocityDB Version 5.3.18 Release Notes

Properly handle serialization of null fields typed as System.Object or as interface. Introducing ServerClientSessionShared for shared reads from VelocityDBServer with multiple concurrent threads.

VelocityDB Version 5.3.11 Release Notes

Fix for updating assembly version in persisted type strings. Schema is updated when using a different VelocityDB assembly version compared to version used by prior update transaction. This is unfortunate but currently required because current .Net class loader is using assembly version when resolving a Type. Any better ideas?

Fix for handling of closed network streams in VelocityDBServer.

VelocityDB Version 5.3.8 Release Notes

Enable multiple threads/sessions and processes to add objects, including same type of object, concurrently using ServerClientSession. NUnit test in MultipleUpdaters.cs updating to test this.

VelocityDB Version 5.3.7 Release Notes

Add NUnit test to MultipleUpdaters.cs for testing with multiple sessions and multiple threads adding same object type to a couple of databases using ServerClientSession. Fix a couple issues found by this new test. Allow reading previously committed page from VelocityDBServer with pessimistic locking while page is updated by another transaction.

VelocityDB Version 5.3.5 Release Notes

Verified to work with Microsoft Azure cloud file storage. Added prototype AzureSession class (project VelocityDbExtensions). AzureSession is still work in progress but using shared Azure drives directly using “net use” commands works OK.