This topic describes the purpose and uses of versioning.
Tools and applications use a set of classes to represent the data in the Comms Database. These classes are the container classes, which derive from CMDBElement and MMetaDatabase.
The format of the data does not match the format of the data in the database. The implementation of the CommsDat API maps between the external format and the internal format.
Future releases of Symbian platform can change the internal format. The map between the external format and the internal format maintains compatibility for tools and applications if the internal format changes.
A new internal format is a new version of the interface. If a new version is created, the older version is deprecated, but Symbian platform maintains the compatibility for a managed period.
You specify the version you need when you create a session with the Comms Database.
A version is defined by an instance of the TVersion class.
In practice, changes to versions are extremely rare. The curent version is the same version used when the Comms Database was added to Symbian platform.