how to design member registration process for your web site?

You create the following list of information that you want to store when customers register for the Members Only section of your Web site:

• Member name
• Member address
• Member phone number
• Member fax number
• Member e-mail address

In addition, you would like to collect the date when the member registers and track how often the member goes into the Members Only section. You design the Members Only database by following the steps presented in the “Organizing data in tables” section, earlier:

• Name your database. The database for the Members Only section may be named MemberDirectory or other.
• Identify the objects. The information list is
• Member name
• Member address
• Member phone number
• Member fax number
• Member e-mail address
• Member registration date
• Member logins

All this information pertains to members, so the only object for this list is member.

• Define and name a table for each object. The MemberDirectory database needs a table called Member.
• Identify the attributes for each object. Look at the information list in detail:
• Member name: Two attributes: first name and last name.
• Member address: Four attributes: street address, city, state, and zip code. Currently, you have pet stores only in the United States, so you can assume that the member address is an address in the U.S. mailing address format.
• Member phone number: One attribute.
• Member fax number: One attribute.
• Member e-mail address: One attribute.
• Member registration date: One attribute.

Several pieces of information are related to member logins:

• Logging in to the Members Only section requires a login name and a password. These two items need to be stored in the database.
• The easiest way to keep track of member logins is to store the date and time when the user logged into the Members Only section. Because each member can have many logins, many dates and times for logins need to be stored. Therefore, rather than defining the login time as an attribute of the member, define login as an object, related to the member, but requiring its own table.

The added table is named Login. The attribute of a login object is its login time (the time includes the date).

• Define and name the columns. The Member table has one row for each member. The columns for the

Member table are

• loginName
  
• password
  
• createDate
  
• firstName
  
• lastName
  
• street
  
• city
• state
• zip
• email
• phone
• fax

The Login table has one row for each login: that is, each time a member logs into the Members Only section. It has the following columns:

• loginName: The login name of the member who logged in. This is the column that links this table to the Member table. This value is unique in the Member table but not unique in this table.
• loginTime: The date and time of login.
• Identify the primary key.
• The primary key for the Member table is loginName. Therefore, loginName must be unique.
• The primary key for the Login table is both loginName and loginTime together.
• Define the defaults. No defaults are defined for either table.
• Identify columns with required data. The following columns should never be allowed to be empty:
• loginName
• password
• loginTime

These columns are the primary key columns. A row without these values should never be allowed in the tables.