Eloquera Database is an object database for .NET environments. It has several unique features which make it highly attractive to enterprise and desktop application developers.
In practical experience, Eloquera provides development times approximately half of the current, combined with production performance gains that can be orders of magnitude better, increasing as the complexity of the DB structure.
From version 4.0 Eloquera DB supports stored procedures – or better to call them “stored methods”? The notion of the stored procedures (SP) is well-known to those with experience in the relational databases: SPs are blocks of code, which can be invoked on
the database side, usually to perform multiple data operations or to validate input data against existing data.
If TypeUpdateAllowed is turned on, while storing a new object, database will auto-detect
• Changes in field’s type. Already stored objects' fields will be converted to a new type.
• Newly added fields. Old objects will be converted to a new type, with new fields assigned a default value.
• Removed fields.
None
0 Points
7 Posts
Eloquera DB 4 - Stored Procedures, Schema Evolution
Sep 21, 2011 07:35 AM|eloquera|LINK
Eloquera
www.eloquera.com
Eloquera DB 4 has been released.
Eloquera Database is an object database for .NET environments. It has several unique features which make it highly attractive to enterprise and desktop application developers.
In practical experience, Eloquera provides development times approximately half of the current, combined with production performance gains that can be orders of magnitude better, increasing as the complexity of the DB structure.
Eloquera 4 release notes
1) Stored Procedures
From version 4.0 Eloquera DB supports stored procedures – or better to call them “stored methods”? The notion of the stored procedures (SP) is well-known to those with experience in the relational databases: SPs are blocks of code, which can be invoked on the database side, usually to perform multiple data operations or to validate input data against existing data.
2) From version 4.1 Eloquera supports native type evolution.
Eloquera.config contains TypeUpdateAllowed tag that determines whether type changes shall be auto detected and applied.
<div class="geshifilter"> <div class="csharp geshifilter-csharp"><SmartRuntime Smart="true" TypeUpdateAllowed ="true" /></div> </div>If TypeUpdateAllowed is turned on, while storing a new object, database will auto-detect
• Changes in field’s type. Already stored objects' fields will be converted to a new type.
• Newly added fields. Old objects will be converted to a new type, with new fields assigned a default value.
• Removed fields.
A function to rename type is also available
<div class="geshifilter"> <div class="csharp geshifilter-csharp">void RenameType(Type type, string oldTypeName);</div> <div class="csharp geshifilter-csharp"></div> </div>
3) Corrupted database recovery
With version 4.0 a corrupted database recovery mechanism is added.
4) New ways to optimize database performance
5) Store speed increased 2-4 times
6) Database can work without explicit configuration.
Database will auto-detect path and create database in the same folder with server executable file if no path is specified programmatically.