StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19906626
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-11T12:41:26.487
FavoriteCount
0
LastActivityDate
2013-11-11T12:41:26.487
LastEditDate
LastEditorUserId
0
OwnerUserId
1226722
ParentId
19736928
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Turns out there was a subtle problem with my <code>settings.py</code> splitting method. For anyone coming here from Google, I was following <a href="http://www.deploydjango.com/django_project_structure/index.html#building-a-perfect-django-settings-module" rel="nofollow">deploydjango.com</a>'s and strategy on splitting <code>settings.py</code>, however <code>ROOT_DIR</code> was being defined in terms of the project, i.e. the following structure <pre><code>$ tree -L 2 . ├── static ├── apps └── project ├── __init__.py ├── settings │ ├── __init__.py │ ├── base.py │ ├── dev.py │ └── prod.py ├── urls.py └── wsgi.py </code></pre> with the following setting <pre><code>STATICFILES_DIRS = ( ABS_PATH('apps', 'example_app', 'static'), ) </code></pre> would result in <code>ROOT_DIR</code> being set to <code>project/</code>. And since <code>ABS_PATH</code> function defines paths based on <code>ROOT_DIR</code>, the <code>apps/</code> folder is not visible (it should be preceded with <code>'..'</code>). The solution is of course to move <code>apps/</code> folder inside the <code>project/</code> folder, which makes sense. I.e. the correct structure is as follows: <pre><code>$ tree -L 2 . ├── static └── project_name ├── __init__.py ├── apps # <-- apps moved here │ └── example_app ├── settings │ ├── __init__.py │ ├── base.py │ ├── dev.py │ └── prod.py ├── urls.py └── wsgi.py </code></pre> I realised this problem is very tied to the way I was doing things, however since this structure can be seen by some people as "best practice" (although <a href="http://bruno.im/2013/may/18/django-stop-writing-settings-files/" rel="nofollow">some disagree</a>), I hope this helps someone!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODjango.staticfiles doesn't collect admin files
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USgregoltsov
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODjango.staticfiles doesn't collect admin files
 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
 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.