Refer to the following database diagram to gain an understanding of the database structure used by SoftSlate Commerce. For more details about the attributes of each table's fields, refer to the Database Dictionary .
SoftSlate Commerce Database Schema. Larger Image.
Here is a list of some of the notable aspects of the database structure:
- The
sscSettingtable stores all of the application's settings. It is designed to store settings of various data types. For each record, the value of thevalueTypefield identifies which field is used to store the setting's value. In the application, the values are derived andsscSettingis converted into ajava.util.HashMapin which thecodevalue is the map's key. This map is stored in the application scope. - Both complete and incomplete orders are stored side by side in the
sscOrdertable. Incomplete orders store a representation of the user's cart before completing checkout in the store. To test if a given order is complete, check that itscompletedfield is not null. A tool exists in the Administrator (under theMaintenance and Upgrademenu), to clear out old incomplete orders from the database. - The
sscOrderandsscCustomertables store the user's billing address, where as thesscOrderDeliveryandsscCustomerAddresstables store delivery addresses. There may be many delivery addresses per order and per customer. However, the application's code does not currently support the notion of delivering a single order to multiple addresses, or storing multiple delivery addresses for each customer account.