Extending membership tables in asp.net ?

Question

0.00/5 (No votes)

See more:

Hi all ,

I added a table called user info that contains data that i need for my application and not founded in the membership tables.So in this table i have a unique identifier field called user_id.I need to relate this field to membership tables.So to which one should i relate it ? to users table or membership table ?

Thanks in advance.

Posted 8-Aug-11 22:54pm

mhamad zarif

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Syed Salman Raza Zaidi · Answer 1 · 2011-08-08T23:08:00

Solution 1

The one in which you are storing your user information,i suggest you to store in membership table

Posted 8-Aug-11 23:08pm

Syed Salman Raza Zaidi

_Zorro_ · Answer 2 · 2011-08-08T23:38:00

Solution 2

Have a look at this:

Implementing a Membership Provider[^]

Hope it helps.

Posted 8-Aug-11 23:38pm

_Zorro_

sujit0761 · Answer 3 · 2011-08-08T23:38:00

Another option with you is that you can create a new table with the user_id as foreign key to it. The advantage of using a seprate table will be that you can add as many features as you want without affecting the current mebership tables.All you have to do is to make snall changes in procedures where value gets insert in these membership tables