Blog

Referential integrity is one of the most important features of the relational databases because entities like Employee are referred by their artificial keys, like Employee.ID field in the Employee table.
The object and document-oriented databases like the Eloquera DB (which is both, actually) use the object references instead of referencing by the external keys. For example, Payment object may contain a property of the Employee type for referencing to the right person:

Eloquera Database is a free closed source product. Eloquera Database as per design and per corporate roadmap targets enterprise level market, not an embedded applications.
We were asked a numerous times about database internals, though we cannot disclose internal API or source code we can provide with a general overview how database looks inside.
Keep in mind that below picture intends to give an overall idea only. Database is a complex product, with a number of patents pending and with sophisticated logic inside, which is very hard to describe in one picture.

Bulk inserts in fact are handled by the same Store method used for storing any other object.
You simply store an array - and the database will take care of everything, e.g. database will find all dependencies and store them (see Store Method (obj)).

Example 1:

In the version 3.0 of the Eloquera Database we have introduced a new functionality that we call dynamic objects. From the point of view of the documentation, it is a minute change – just a new class called Dynamic in the Eloquera.Client namespace. But it adds new magic to the developer’s treasury of tricks.