Database structure of asp.net 2.0 providers

  • Thread starter Thread starter Arjen
  • Start date Start date
A

Arjen

Hi,

I have some questions about the database structure used by the asp.net 2.0
providers.

Why are the tables aspnet_users and aspnet_membership not one table?

Why is the userId of type uniqueidentifier and not int32?

For all the questions... what are the advantages or this advantages.

Thanks!
 
Why are the tables aspnet_users and aspnet_membership not one table?

Because for the other Sql-related providers (profile, personalization, etc)
they factoroed out a table for the user information. So the user table is
shared across all the providers. This is an implementation detail. They could
have just as easily put all of the user information into each of those tables,
but I suspect they thought that was redundant.
Why is the userId of type uniqueidentifier and not int32?
Click to expand...

I don't know specifically why they chose this approach. But in general you
would tend to use a guid for DB portability.

-Brock
DevelopMentor
http://staff.develop.com/ballen
 
I don't know specifically why they chose this approach. But in general
you would tend to use a guid for DB portability.
Click to expand...

Possible scenario:
If the programmer later wanted to merge user tables from other applications
each user would be uniquely identified and there would be no ID conflicts.
 
Back
Top