StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10662358
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-05-19T04:44:47.563
FavoriteCount
0
LastActivityDate
2012-05-19T04:44:47.563
LastEditDate
LastEditorUserId
0
OwnerUserId
497043
ParentId
10662278
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Doctests are formatted in just the same way as you would run an interactive session. You can run an interactive session and just copy it and you'll get all the results. This might be one valid session: <pre><code>>>> import datetime >>> print Manager(10, 'Bob', 'Quux', '123', datetime.datetime(2009, 1, 1), ... ['Michael', 'Bob', 'Hello']) 10, Bob Quux, 123, 0001-01-01 00:00:00, 2009-01-01 00:00:00, Michael, Bob, Hello >>> print Manager(2000, 'Bob', 'Lol', '1234', datetime.datetime(2009, 1, 1), ... ['Michael', 'Bob', 'Hello']) 2000, Bob Lol, 1234, 0001-01-01 00:00:00, 2009-01-01 00:00:00 </code></pre> There were assorted syntax errors in what you had done; <ul> <li>For the doctest part of it, if you're continuing the statement, the next line must start with <code>... </code> (exactly the same as in a regular session);</li> <li>Your <code>Manager</code> instantiation was invalid (genuine Python <code>SyntaxError</code>) as you had <code>startDate=...</code> (a keyword argument) followed by a non-keyword argument (the value for "manager"). This is the main problem that stopped it from running. And that's also what the exception told you.</li> </ul> If you can't figure it out in a doctest, run it in a normal Python session. Play with it there. There are also a number of other significant problems in your code; here are a couple of them: <ul> <li><code>EmpSalaried</code> versus <code>Employee</code>: what gives with that?</li> <li>Due to using a mutable default argument, if you don't specify the <code>manage</code> argument when creating a <code>Manager</code>, they will get the same list. This is not what you want.</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POTrouble getting doc tests to pass in python
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USChris Morgan
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POTrouble getting doc tests to pass in python
 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.