The communications database

Communications settings are held in the form of individual tables within a single database managed by CommDb. The classes provided by CommDb use DBMS in their implementation and it is DBMS which provides the underlying behaviour for handling the database itself. In effect, CommDb is a layer over DBMS.

The tables are as follows:

Major changes in Version 8.1 are:

• new fields in the Global Settings Table to store CDMA SimpleIP and MobileIP capability parameters

• new fields in the Default CDMA2000 Settings table to store non NAI-specific configuration settings that can be provisioned OTA

• new fields in the Default CDMA2000 Settings table to store NAI-specific configuration settings that can be provisioned OTA

Major changes in Versions 7.0s are as follows:

• new NETWORK table

• new MODEM_BEARER table, replacing the previous MODEM table

• new LAN_BEARER table

• The agent table has been removed and its fields have been relocated to other tables

Major changes in Versions 7.0 are as follows:

• new CDMA2000_PACKET_SERVICE_TABLE and DEFAULT_CDMA2000_SETTINGS_TABLE tables to support CDMA2000 settings.

Major changes in Versions 6.1 are as follows:

• New support for storing information relating to connecting through GPRS.

• The DIAL_OUT_IAP and DIAL_IN_IAP tables have been united into a single IAP table.

• The Global table no longer stores information about a default connection. Instead, a Connection preferences table is provided that stores connection options ranked by preference. This global setting for whether to prompt the user to choose a service before dialling is also replaced by a setting for dialog preference in the Connection preference table.

Version 6.0 compatibility

Version 6.0 of CommDb allowed clients the option of two different database structures: termed IAP- and ISP-type databases respectively. IAP (Internet Access Point)-type databases provides an IAP table that allows an ISP record and a chargecard to be identified as a group. An ISP-type database does not have an IAP table, but is otherwise identical.

Despite the table changes between Versions 6.0 and 6.1, the CommDb API still supports clients written to use Version 6.0. In particular, note the following:

• Calls that use the old IAP tables are translated to use the new IAP table.

• Calls that use the old Global table are translated to use the Connection preferences table. For details, see the documentation for CCommsDatabase::SetGlobalSettingL() and CCommsDatabase::GetGlobalSettingL().