I am fairly new to MVC and am starting a project that requres membership.
The project uses teams/groups in that when you register and log in you will be able to navigate to a group page etc. Within each group there are admins and general users.
I want to know what the best practice in terms of the db backend would be to set up and begin such a project. I currently have the unaltered membership logic that ships with MVC 4. Is it best to link the membership table in with a userProfile table to
store there profile information and also link it with a teamDetails table...apologies if this question is vague or stupid.
Is it best to link the membership table in with a userProfile table to store there profile information and also link it with a teamDetails table
I don't see any problem with that, you need to link it anyway to get the profile information. The other table I am not sure what is the intention but if you are using username as primary key, you can use but I would use some other unique id which is common
for my project and just membership specific.
Ok the userProfile table (which I will make within the membership DB) would be used to store personal information for a person such as name, date of birth, contact details etc. TeamDetails table (again within the same DB) would hold things like teamName,
teamAddress, teamContactNumber (team as in a sports club).
Was wondering though if it would be better practice to create another database entirely to store these app data tabels such as userProfile and teamProfile?
JM1990
Member
1 Points
5 Posts
MVC 4 and membership
Nov 13, 2012 04:15 PM|LINK
I am fairly new to MVC and am starting a project that requres membership.
The project uses teams/groups in that when you register and log in you will be able to navigate to a group page etc. Within each group there are admins and general users.
I want to know what the best practice in terms of the db backend would be to set up and begin such a project. I currently have the unaltered membership logic that ships with MVC 4. Is it best to link the membership table in with a userProfile table to store there profile information and also link it with a teamDetails table...apologies if this question is vague or stupid.
Appreciate your responses
CPrakash82
All-Star
18284 Points
2841 Posts
Re: MVC 4 and membership
Nov 13, 2012 06:08 PM|LINK
I don't see any problem with that, you need to link it anyway to get the profile information. The other table I am not sure what is the intention but if you are using username as primary key, you can use but I would use some other unique id which is common for my project and just membership specific.
JM1990
Member
1 Points
5 Posts
Re: MVC 4 and membership
Nov 14, 2012 10:07 AM|LINK
Thanks for the response!
Ok the userProfile table (which I will make within the membership DB) would be used to store personal information for a person such as name, date of birth, contact details etc. TeamDetails table (again within the same DB) would hold things like teamName, teamAddress, teamContactNumber (team as in a sports club).
Was wondering though if it would be better practice to create another database entirely to store these app data tabels such as userProfile and teamProfile?
CPrakash82
All-Star
18284 Points
2841 Posts
Re: MVC 4 and membership
Nov 14, 2012 10:52 AM|LINK
Creating User Profile table within membership db is fine but any other table I would suggest to do it outside and track it with your own identifier.
JM1990
Member
1 Points
5 Posts
Re: MVC 4 and membership
Nov 14, 2012 08:03 PM|LINK
Ok so in that case I might as well keep aspnet db completely seperate from AppNameDB...
CPrakash82
All-Star
18284 Points
2841 Posts
Re: MVC 4 and membership
Nov 14, 2012 09:08 PM|LINK
Correct.
JM1990
Member
1 Points
5 Posts
Re: MVC 4 and membership
Nov 15, 2012 10:48 AM|LINK
Thanks! Appreciarte the help with this