StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1967060
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-12-27T21:14:34.253
FavoriteCount
0
LastActivityDate
2009-12-27T21:31:03.813
LastEditDate
2009-12-27T21:31:03.813
LastEditorUserId
57100
OwnerUserId
57100
ParentId
1966579
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
If those are "parts" to the same application, you should separate them using URL mappings instead, this way maintenance is easier (since the url endpoints will be "centralized" and you'll be editing them in python) and everything gets more concise (app.yaml maps applications). <a href="http://code.google.com/appengine/docs/python/tools/webapp/running.html" rel="nofollow noreferrer">Read this for clarification</a> You'd basically add new mappings to several different handlers and organize those as python modules. <pre><code>(...) from myapp import Part1, Part2 # etcetera (...) application = webapp.WSGIApplication([('/part1', Part1), ('/part2', Part2])]) </code></pre> In case you're having trouble modularizing your python code, perhaps reading <a href="http://docs.python.org/tutorial/modules.html#packages" rel="nofollow noreferrer">the official docs</a> will help. EDIT: My answer above is basically the same as the first one, it wasn't there when I started answering, sorry. A little more clarification on why this is better than having each part as a separate application: <ul> <li>Module loading will only happen once per application restart</li> <li>If you check your appengine dashboard, some modules may take a long time to load (mostly when they're big, obviously)</li> <li>Profiling your whole set would be just a matter of adding a Middleware to <code>application</code>.</li> </ul> Even with all that, I think the most important point would be: code organization will be way easier to accomplish since you can separate applications and logics in individual packages/applications.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGoogle App Engine Python WebApp - Am I doing this right?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCaio Romão
UserOwnerUserId
1. USCaio Romão
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POGoogle App Engine Python WebApp - Am I doing this right?
 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
 VTAcceptedByOriginator
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.