Try OpenEdge Now
skip to main content
Programming Interfaces
Database Administration Entity Collection Interface Reference : Collection interface naming conventions

Collection interface naming conventions

In general, the name of each collection interface consists of the following components:


Identifies the name of an interface.
The name of the entity that the interface represents, for instance, Domain or Tenant.
The type of collection, which can contain multiple instances of Entity. This can be one of the following:
*Collection — Used for a few base interfaces and classes, for instance, IDataAdminCollection, which is inherited by all collection interfaces.
*List — Used for collections that are an ordered collection (sequence), for instance, IExtentList (currently the only list).
*Map — Used for collections that map entity values to keys (with no duplicate keys), for instance, IPartitionMap and ISequenceValueMap. In effect, entity maps relate collections of entities in many-to-many relationships, such as a collection of multi-tenant sequences mapped to a collection of tenants through the sequence values (the ISequenceValueMap).
A Map is not used to map scalar keys of type INTEGER or CHARACTER. Instead, collections can have Find( ) and CanFind( ) methods for scalar properties (keys).
*Set — Used for a collection of entities that contain no duplicate elements.