Custom Membership - what to store in User Profile?

[wmin3]

Hi, should I store detailed user information such as first, middle & last names, job title, dob in standard Users table - created automatically or should I create a separate table to strore this information?

Thanks!

wmin

 

[jdemmi]

personal preference -- i usually see the basics in the "person/user" table and then the details/options in a "user/person" profile table.

-- Jason
"It's Just Ones and Zeros

 

[wmin3]

Jason thanks, I don't want to sound daft but what is the difference between "person/user" and "user/person" tables? I am not sure I am following you

 

[jdemmi]

Here's an example of what I was referring to

TABLE 1
TBL_EMPLOYEE
COL1 = EMP_ID
COL2 = EMP_FNAME
COL4 = EMP_MNAME
COL3 = EMP_LNAME
COL3 = EMP_EMAIL


TABLE 2
TBL_EMPLOYEE_PROF
COL1 = EMP_ID
COL2 = EMP_ADDRESS1
COL4 = EMP_ADDRESS2
COL3 = EMP_CITY
COL3 = EMP_STATE
COL4 = EMP_ZIP
COL5 = EMP_TITLE
COL6 = EMP_MEMO

That's the jist of it....

-- Jason
"It's Just Ones and Zeros

 

[wmin3]

Hi Jason, thanks for your explanation, however, I was thinking of .NET 2/3 Membership Class which automaticaly generates tables for you including:

aspnet_Users - table
------------
ApplicationID
UserID
UserName
LoweredUserName
MobileAlias
IsAnonymous
LastActivityDate

I was wondering if I should extend this automaticaly generated table OR create my own with UserID as foreign key,
which would contain detailed user info.

What is the best practice?

Thanks, once again

 

[jbenson001]

In the past, I have added columns I needed to the membership tables.