StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19169815
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-03T21:47:11.197
FavoriteCount
0
LastActivityDate
2013-10-03T21:47:11.197
LastEditDate
LastEditorUserId
0
OwnerUserId
215057
ParentId
18033165
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
SimpleMembershipProvider is not email aware. It literally has no concept of email as you'll note if you look at the default auto-generated schema. This is why many of the legacy MembershipProvider APIs are unsupported by the SimpleMembershipProvider implementation. You can of course add an email column to the UserProfile table (as I assume you've done), but the provider has no mechanism for implementing RequiresUniqueEmail, and is in fact hardwired to always return false. Adding a database constraint will work to some extent but only by causing an Exception when the the profile is updated. It's not at all elegant, but should work. You could tell SimpleMembershipProvider to use email as username when initializing the provider, but this means losing userName field and requiring users to login with email/password which may not be preferable. <pre><code>WebSecurity.InitializeDatabaseConnection(connectionString, "UserProfile", "UserId", "Email", true); </code></pre> An alternative is to extend the SimpleMembershipProvider, make it email aware, and implement RequiresUniqueEmail. Take a look at <a href="https://github.com/TheCodeKing/BetterMembership.Net" rel="nofollow">BetterMembership.Net</a> on GutHub, it does exactly that and can be used as a replacement for SimpleMembershipProvider. The email column is specified on the provider, and it supports RequiresUniqueEmail out-of-the-box. <pre><code><add name="BetterProvider" type="BetterMembership.Web.BetterMembershipProvider, BetterMembership, Version=1.0.1.0, Culture=neutral, PublicKeyToken=737bc70442f2c4af" connectionStringName="DefaultConnection" userIdColumn="UserId" userNameColumn="UserName" userTableName="UserProfile" userEmailColumn="Email" requiresUniqueEmail="true" autoInitialize="true" /> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORequiresUniqueEmail in SimpleMembershipProvider
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USTheCodeKing
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.