J
Jonathan Wood
I'm using the ASP.NET membership routines but had to create some of my own
tables to store additional user information (profiles won't work for me).
So far, so good. But it seems like I should really create a relationship
between the membership table aspnet_Membership and my own table in order to
have the database enforce the relationship, and, ideally, to also implement
automatically cascading deletes to avoid orphaned records in my own tables.
So I created a foreign key in my own table, and set up a relationship with
the UserId field in aspnet_Membership. But I'm new to this and I notice that
this makes a change to the aspnet_Membership table (VS tells me both tables
need to be saved).
I'm a little uncomfortable making changes to the existing tables. I'm not
completely certain I've set up the relationship correctly and would hate to
disable the membership tables and also I wonder about what happens if the
membership tables must be recreated for some reasons.
Anyone have any tips for me?
Thanks!
tables to store additional user information (profiles won't work for me).
So far, so good. But it seems like I should really create a relationship
between the membership table aspnet_Membership and my own table in order to
have the database enforce the relationship, and, ideally, to also implement
automatically cascading deletes to avoid orphaned records in my own tables.
So I created a foreign key in my own table, and set up a relationship with
the UserId field in aspnet_Membership. But I'm new to this and I notice that
this makes a change to the aspnet_Membership table (VS tells me both tables
need to be saved).
I'm a little uncomfortable making changes to the existing tables. I'm not
completely certain I've set up the relationship correctly and would hate to
disable the membership tables and also I wonder about what happens if the
membership tables must be recreated for some reasons.
Anyone have any tips for me?
Thanks!