StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18902707
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-09-19T18:50:54.567
FavoriteCount
0
LastActivityDate
2013-09-19T18:50:54.567
LastEditDate
LastEditorUserId
0
OwnerUserId
2304092
ParentId
18790188
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
<blockquote> <ol> <li>Would like advice on how to debug why this is not working.</li> </ol> </blockquote> You can use the <a href="https://docs.djangoproject.com/en/dev/topics/logging/#module-django.utils.log" rel="nofollow">python / django logging mechanism</a> and throw logging information wherever needed. In short: <pre><code>import logging logger = logging.getLogger(__name__) # Get an instance of a logger my_custom_command = "/usr/local/build " + self.site + ' ' + self.num + ' ' + self.octet logger.warning(my_custom_command) </code></pre> prints a warning message to console. If you use the <a href="https://pypi.python.org/pypi/django-debug-toolbar" rel="nofollow">django debug toolbar (highly recommended!)</a>, you can easily log using the .debug-level (not .warning) and see the results on the web page. You can include those logging messeges on every intended step of your work flow and check whether everything is as it should be. I'm doing something like this (compiling c-code which is prvided by the user) using the following code snipplet: <pre><code> try: cfile = os.path.join(MEDIA_ROOT, 'temp/src/cfile.c') ofile = os.path.join(MEDIA_ROOT, 'temp/src/cfile.o') efile = os.path.join(MEDIA_ROOT, 'temp/src/cfile.exe') command_string = 'gcc -O0 -g3 -Wall -c -fmessage-length=0 ' + cfile + ' -o ' + ofile compile_result = subprocess.check_output(command_string,stderr=subprocess.STDOUT,shell=True) if compile_result != "": #Compile error self.ausgabe = "Compile:\n" self.ausgabe += str(compile_result) except: self.ausgabe = u"Compilierfehler:\n" self.ausgabe += str(compile_result) </code></pre> (please ignore the German words, they are not important for understanding the logic) One additional thing which might be important is to use correct encoding for all strings. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODjango execute cmd application
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USOBu
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
CommentsPostId
1. COThanks for the help!
 singulars
 PostPostId
 PO
 UserUserId
 USLinuxBill

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.