Telerik OpenAccess Classic

Telerik OpenAccess ORM Send comments on this topic.
User-defined Interfaces
Programmer's Guide > OpenAccess ORM Classic (Old API) > Programming With OpenAccess > The .NET Data Model > User-defined Interfaces

Glossary Item Box

This documentation article is a legacy resource describing the functionality of the deprecated OpenAccess Classic only. The contemporary documentation of Telerik OpenAccess ORM is available here.

With OpenAccess ORM, it is possible to define persistence capable .NET Framework interfaces (Refer to Creating Persistence Capable Classes and The Persistent Attribute for more information about how to make user-defined classes and interfaces persistence capable). In OpenAccess ORM, classes that implement one or more persistence capable interfaces, behave as if they inherit from persistence capable classes (similar to multiple inheritance). In an OpenAccess ORM database, instances of these interfaces have their own object identity.

You can also use an interface type as a data member for a user-defined .NET Framework type to ensure that only objects that implement the specific interface can be assigned to the data member.