StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5272219
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-03-11T11:17:41.920
FavoriteCount
0
LastActivityDate
2011-03-11T11:17:41.920
LastEditDate
LastEditorUserId
0
OwnerUserId
10661
ParentId
5268588
PostTypeId
2
Score
8
ViewCount
0
LastEditorDisplayName
text
Body
<blockquote> the required steps for a Django application? </blockquote> There are two required steps. Write the settings. Write the urls.py The rest of the steps are optional. <blockquote> This also serves as a checklist of things to do. </blockquote> Bad policy. You don't need a checklist of Django features. You need a collection of use cases or user stories which you must implement. For some reason, you've omitted the two most important and valuable features of Django. Configure the default admin interface and write unit tests. The default admin interface is very high value. Unit testing is absolutely central. You do it like this. <ol> <li>Gather use cases.</li> <li>Prioritize the use cases.</li> <li>Define the actors. The classes of actors becomes groups in the security model.</li> <li>Define enough "applications" to satisfy the first release of use cases. Define the url structure. Cool URL's don't change. </li> <li>Build the first use case: models (including security), admin, urls, tests, forms, views and templates. Note that these are the file names (models.py, admin.py, ...) except for templates. Also note that forms and admin should be defined in separate modules even though this isn't required. Also note that templates will be split between a generic templates directory for top-level stuff and application-specific templates.</li> <li>Build the second use case: models (including security), admin, urls, tests, forms, views and templates.</li> </ol> ... n. Package for release. Tweak up the settings. Configure database and mod-wsgi
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat is a good Django workflow?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USS.Lott
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. 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.