B
Bogdan
Hi,
I'd like to take a full advantage of built-in membership services and use
aspnetdb's UserId in my app's database. For example, I'd like to establish
some relationships between membership users from aspnetdb and rows in tables
in my database. My app would be responsible for enforcing the
cross-database 'referential integrity'. Does this sound as a
good/acceptable practice?
Thanks,
Bogdan
I'd like to take a full advantage of built-in membership services and use
aspnetdb's UserId in my app's database. For example, I'd like to establish
some relationships between membership users from aspnetdb and rows in tables
in my database. My app would be responsible for enforcing the
cross-database 'referential integrity'. Does this sound as a
good/acceptable practice?
Thanks,
Bogdan