MMv4 KB
 
admin DB Table
  Last Edited - 05/17/2010 4:10pm PDT
  Category Path - Developer's Guide > Database Structure
 
This article outlines the database structure for the MMv4 admin database table.

  • id
    Primary Key of admins table.
    int(10) | unsigned | auto increment | primary key | indexed
  • active
    Admin account's active status. Inactive admins are not allowed to access the store's administration area.
    int(10) | unsigned | Values: 0/timestamp | Default: 1 | indexed
  • login
    The moniker associated with the administrator. The login will be used to access the administration area and will be used to identify the admin's forum, blog, kb, QC glossary and support ticket posts.
    varchar(255) | indexed
  • email
    The admin's email address. Support Ticket responses and other communication from Modular Merchant to the admin will be sent to this email address.
    varchar(255)
  • first_name
    The admin's first name. This may be displayed in various places in the store's administration and Support Ticket areas.
    varchar(255)
  • last_name
    The admin's first name. This may be displayed in various places in the store's administration and Support Ticket areas.
    varchar(255)
  • address_1
    The first line of the admin's address. The name of this field has changed from "address1" in MMv3.
    varchar(255)
  • address_2
    The second line of the admin's address.
    The name of this field has changed from "address2" in MMv3.
    varchar(255)
  • city
    The city of the admin's address.
    varchar(255)
  • state
    The two-character ISO code for the state of the admin's address, followed by the two-character ISO code for that state's country.
    varchar(255) | Format: State-ISO_Country-ISO (Example: OR_US)
  • zip
    The zip code of the admin's address.
    varchar(255)
  • country
    The two-character ISO code for the country of the admin's address.
    varchar(255)
  • phone_ac
    The area code of theadmin's primary phone number.

    varchar(255)
  • phone
    The admin's primary phone number.
    The name of this field has changed from "phone1" in MMv3.
    varchar(255)
  • question
    The admin's security question. Modular Merchant technicians will ask this question to verify the admin's identity.
    varchar(255)
  • answer
    The answer to the admin's security question.
    varchar(255)
  • handle
    The user name appended to any forum, blog, QC glossary or KB post made by the admin.
    varchar(255)
  • signature
    The admin's signature will be appended to any forum, blog, QC glossary, KB or Support Ticket posts made by the admin.
    text
  • avatar
    The file name of the admin account's avatar image.
    varchar(255)
  • color
    The color associated with the admin account. Used in charts, reports, etc.
    varchar(255)
  • work_area_width
    The work area width for this specific admin account.
    int(10)  | unsigned | indexed
  • font_size
    The font size for the administration area for this admin account.
    int(10) | unsigned | indexed



DEPRECATED TABLE FIELDS (Field not retained from v3)

  • admin_type
    Replaced by the admin-specific permission levels recorded in the prefs/_(ADMIN-ID)_admin_permissions.xml file.
  • password
    Replaced by the admin_passwords DB table, which will be required in order to record the admin's last X passwords. PCI compliance requires that the admin's passwords are forced to be changed every X days, and that the new password cannot be the same as any of the X most recent passwords.
  • company
    Replaced by the custom fields that can be created for admin accounts.
  • phone2
    Replaced by the custom fields that can be created for admin accounts.
  • fax
    Replaced by the custom fields that can be created for admin accounts.
  • create_date
    This field is obsolete because it this information will be recorded in the Admin Activity report.
  • edit_date
    This field is obsolete because this information will be recorded in the Admin Activity report.
  • edited_by
    This field is obsolete because this informaiton will be recorded in the Admin Activity report.
  • color
    Both the customizable avatar and the custom admin fields that can be created make this field obsolete.
  • forum_sig
    The "signature" field will replace the separate "forum_sig" field.

 

Powered by ModularKB