The Personalization module uses the following tables to store user data. Note that the tables shown, which have the prefix dps, apply to external profiles and are referenced by the ProfileAdapterRepository. A parallel set of tables exists for internal users with the prefix dpi, for example dpi_user. These tables are referenced by the InternalProfileRepository.
dps_user
This table contains information associated with a Personalization module user.
Column | Data Type | Constraint |
|---|---|---|
| VARCHAR(40) | NOT NULL |
(primary key) | The unique identifier associated with the user. | |
| WVARCHAR(20) | NOT NULL UNIQUE |
The user’s login name. | ||
| NUMERIC(1) | NULL |
Determines whether to perform autologin for this user. This value is set by the | ||
| VARCHAR(35) | NULL |
The user’s password. Note that this field must be at least 35 characters long if the Personalization module stores a hash of the password and not the actual value. | ||
| NUMERIC(3) | NULL |
Whether or not the user is a member. | ||
| WVARCHAR(40) | NULL |
The user’s first name. | ||
| WVARCHAR(40) | NULL |
The user’s middle name. | ||
| WVARCHAR(40) | NULL |
The user’s last name. | ||
| INT | NULL |
The user’s type, either (1) investor, (2) broker, or (3) guest. | ||
| INT | NULL |
The user’s locale. | ||
| TIMESTAMP | NULL |
The time the user last accessed the Web site. | ||
| TIMESTAMP | NULL |
The time the user registered at the Web site. | ||
| WVARCHAR(40) | NULL |
The user’s e-mail address. | ||
| INT | NULL |
The status of the user’s e-mail address, for example whether valid or invalid. | ||
| INT | NULL |
Determines whether or not the user is to receive e-mails. | ||
| INT | NULL |
The user’s gender. | ||
| TIMESTAMP | NULL |
The user’s date of birth. | ||
| INT | NULL |
Indicates how a user was assigned to this site, either (0) ANONYMOUS, (1) URL-PARAM, (2) AUTO-SIGNIN, (3) HTTP-BASIC-AUTH, (4) EXPLICIT-SIGNIN, (5) SECURE_SIGNIN, or (6) CERTIFICATE. | ||
dps_contact_info
This table contains information about a user’s contact info. There can be multiple contact infos for a single user, and all this information is stored in this table.
Column | Data Type | Constraint |
|---|---|---|
| VARCHAR(40) | NOT NULL UNIQUE |
(primary key) | The unique identifier associated with the contact information. | |
| VARCHAR(40) | NULL |
The unique identifier associated with the user who owns the contact information. | ||
| WVARCHAR(40) | NULL |
The name prefix (for example, a title) of this user. | ||
| WVARCHAR(40) | NULL |
The first name of this user. | ||
| WVARCHAR(40) | NULL |
The middle name of this user. | ||
| WVARCHAR(40) | NULL |
The last name of this user. | ||
| WVARCHAR(40) | NULL |
The name suffix of this user. | ||
| WVARCHAR(100) | NULL |
The job title of the user at this address. | ||
| WVARCHAR(40) | NULL |
The company name of the user at this address. | ||
| WVARCHAR(50) | NULL |
The street and number of this address. | ||
| WVARCHAR(50) | NULL |
The street and number of this address. | ||
| WVARCHAR(50) | NULL |
The street and number of this address. | ||
| WVARCHAR(30) | NULL |
The city of this address. | ||
| WVARCHAR(20) | NULL |
The state of this address. | ||
| WVARCHAR(10) | NULL |
The postal code of this address. | ||
| WVARCHAR(40) | NULL |
The county of this address. | ||
| WVARCHAR(40) | NULL |
The country of this address. | ||
| WVARCHAR(15) | NULL |
The phone number of the user at this address. | ||
| WVARCHAR(15) | NULL |
The fax number of the user at this address. | ||
dps_user_address
This table contains information about a user’s address.
Column | Data Type | Constraint |
|---|---|---|
| VARCHAR(40) | NOT NULL |
(primary key) | The unique identifier associated with the user. References | |
| VARCHAR(40) | NULL |
The unique identifier associated with the user’s home address. | ||
| VARCHAR(40) | NULL |
The unique identifier associated with the user’s billing address. | ||
| VARCHAR(40) | NULL |
The unique identifier associated with the user’s shipping address. | ||
dps_other_addr
This table contains addresses used by profiles. Commerce applications use this table to store a list of addresses in the table dps_contact_info. The Personalization module can also use this table to set up a one-to-many relationship by adding a table similar to the table dps_contact_info and modifying the userProfile.xml template.
Column | Data Type | Constraint |
|---|---|---|
| VARCHAR(40) | NOT NULL |
(primary key) | The unique identifier of the user who owns the address. References | |
| WVARCHAR(42) | NOT NULL |
(primary key) | The type of address, for example work or home. | |
| VARCHAR(40) | NOT NULL |
The unique identifier associated with the address. | ||
dps_credit_card
(External profiles only.) This table contains information about a user’s credit card. There can be multiple contact credit cards for a single user.
Column | Data Type | Constraint |
|---|---|---|
| VARCHAR(40) | NOT NULL |
(primary key) | The unique identifier associated with this credit card information. | |
| VARCHAR(40) | NULL |
The credit card number. | ||
| VARCHAR(40) | NULL |
The type of credit card (MasterCard, Visa, etc.) | ||
| VARCHAR(20) | NULL |
The month the credit card expires. | ||
| VARCHAR(20) | NULL |
The day of the month the credit card expires. | ||
| VARCHAR(20) | NULL |
The year the credit card expires. | ||
| VARCHAR(40) | NULL |
The billing address of the credit card. | ||
dps_usr_creditcard
(External profiles only.) This table contains credit card information associated with a user.
Column | Data Type | Constraint |
|---|---|---|
| VARCHAR(40) | NOT NULL |
(primary key) | The unique identifier associated with the user. | |
| WVARCHAR(42) | NOT NULL |
(primary key) | The type of credit card, for example MasterCard, Visa, etc. | |
| VARCHAR(40) | NOT NULL |
The unique identifier associated with the credit card. REFERENCES | ||
