membership tables

mrlami · Post by **mrlami** » Wed 18 Mar 2009 22:19

Is there a reason why Devart used 2 different tables to hold user information?

Shalex · Post by **Shalex** » Thu 19 Mar 2009 08:49

We create the membership tables that correspond to Microsoft's standards. Please specify the exact names of the tables that store the duplicated information or give a more detailed description of the problem. dotConnect for PostgreSQL membership tables can be found here: \Program Files\Devart\dotConnect\PostgreSQL\InstallWebTables.sql .

mrlami · Post by **mrlami** » Thu 19 Mar 2009 16:49

After some research I found out you guys use the same schema as MSFT.

- http://superpatrick.files.wordpress.com ... pdated.png
- http://webthinker.wordpress.com/2007/11 ... ip-schema/

npgsql implements theirs in a different way that I thought was better so I assumed that was what microsoft was using (duh)

- http://dev.nauck-it.de/aspsqlprovider/b ... Schema.sql (THEY USE JUST ONE TABLE to store all user information which I thought made sense)

Is there any advantage of making this 2 seperate tables?

Shalex · Post by **Shalex** » Fri 20 Mar 2009 16:28

We use two tables (aspnet_users and aspnet_membership) instead of one (users in npgsql) because some our providers (e.g., Role provider and Profile provider) only need the part of the information, that is stored in the aspnet_users table only, the part of the information from the aspnet_membership table is not used by them. On the other hand, Membership provider needs information from the both tables.