How Constraint instance can be connected

A single constraint descriptor.

Describes the connection between a Constraint and its successor.

To be used by the Query interface.

Describes the smallest persistent entity to which instances are serialized and deserialized from.

Describes a freshly inserted instance for an owner

Table-mapping for types

List of joins.

Descriptor for joining types.

Information passed to the Serializer instances during the deserialization process.

Used to track persistent objects in memory. Does not prevent the referenced objects from being collected by the GC because it uses weak referencing.

Helper interface to transfer name / type pairs within Sorm.

Helper interface to transfer name / value pairs within Sorm.

Nodes are used to describe the various ways types can be connected to each other.

Data for exactly one instance.

List of data for several instances.

This interface holds the result from executing a query against the storage. It loads the requested objects lazily, they will only be created once they are referenced.

Buffers data read from the provider.

The possible operators used by Constrain instances.

A complete ordering description consiting of multpile fields.

A single field with its associated sort order.

Interface for storage providers.

Description of Query.

Cardinality of type relations.

Context information for a (de-)serialization. Provides access to the enclosing session and helps to avoid infinite recursion.

Information passed to the Serializer instances during the serialization process.

Implementations of this interface are responsible for (de-)serializing instances of specific types. If the available standard Serializers are not sufficient, more serializers can be added for specifc projetcs.

The Session interface is the central controller to initiate the serialization and deserialization of instances.

Possible sorting orders.

This interface describes te properties of a registered type as needed for making its instances persistent.