We are in the process of completly redesigning and enhancing the driver from scratch. The plan is to follow a traditional database driver architecture and practices. Performance is also a key factor in the redesign. This should be pre-released in early Q1 2017.
- Written in DNX Release 1 for DNX and .Net 4.5.1 support
- Better handling of ordered edges
- Support for LoadRecord and CreateRecord operations - faster than performing the same action via SQL commands
- Improved mapping code for generic types to/from ODocuments - much faster, avoids repeated reflection
- Support for fetch plans using LoadRecord to pull back a whole tree of objects in one request
- Initial support for transactional create/update/delete - should be much faster than multiple individual SQL commands
- Better support for derived types - .ToUnique will construct a TDerived if the database record is of type TDerived
- Initial support for the OrientDB 2.2 binary protocol
- Automatic schema creation from public properties of C# types (Database.Create.Class().CreateProperties().Run())
Fetching a large block of records from the DB via Database.Load.ORID(orid).FetchPlan(plan) and converting them to typed objects about 6 times faster than original code using SQL commands and old mapping.
Storing a large block of records into the DB via a transaction is about 10 times faster than doing it via individual SQL create statements.
How To Use
This code is still under active development.
For the latest build you can in the driver from NuGet
The unit tests should run cleanly and will start and stop OrientDB on the local machine themselves. You will likely need to change the values in the appsettings.json to point correctly to your local OrientDB install.
For more information look at the Documentation.