StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1137832
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-07-16T14:04:39.500
FavoriteCount
0
LastActivityDate
2009-07-16T14:09:53.563
LastEditDate
2009-07-16T14:09:53.563
LastEditorUserId
71690
OwnerUserId
71690
ParentId
1137777
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
You'll want to go grab django-registration and call it a done: <a href="http://bitbucket.org/ubernostrum/django-registration/wiki/Home" rel="nofollow noreferrer">http://bitbucket.org/ubernostrum/django-registration/wiki/Home</a> <blockquote> This is a simple application which provides flexible user registration for Django-based projects. The default setup implements a fairly common workflow: <ol> <li>User signs up for account.</li> <li>User receives an email containing instructions for activating the account.</li> <li>User activates and begins using the site.</li> </ol> </blockquote> Docs on how to integrate and use it: <a href="http://bitbucket.org/ubernostrum/django-registration/src/tip/docs/overview.txt" rel="nofollow noreferrer">http://bitbucket.org/ubernostrum/django-registration/src/tip/docs/overview.txt</a> It manages the reg key, timeout period and all processing for activating an account. I have used this a few times with slight mods and it is very easy to get going testing using even a gmail account for sending to test. Add this to your settings.py in the app to test with a gmail account: <pre><code>EMAIL_USE_TLS = True EMAIL_HOST = 'smtp.gmail.com' EMAIL_HOST_USER = 'YOURUSERATGOOGLEMAIL@gmail.com' EMAIL_HOST_PASSWORD = 'YOURPASSWORD' EMAIL_PORT = 587 </code></pre> Also, django-profiles is a great addition to this django-registration kit: <a href="http://bitbucket.org/ubernostrum/django-profiles/wiki/Home" rel="nofollow noreferrer">http://bitbucket.org/ubernostrum/django-profiles/wiki/Home</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODjango. Confirming user creation by mail
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USRyan Christensen
UserOwnerUserId
1. USRyan Christensen
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODjango. Confirming user creation by mail
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.