StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5370576
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-03-20T18:40:26.763
FavoriteCount
0
LastActivityDate
2015-09-13T16:46:47.757
LastEditDate
2015-09-13T16:46:47.757
LastEditorUserId
509648
OwnerUserId
311220
ParentId
5205417
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
You can also achieve what you want using the <a href="http://docs.python.org/library/email.html" rel="nofollow noreferrer"><code>email</code> module</a>'s <a href="http://docs.python.org/library/email.parser.html#parser-class-api" rel="nofollow noreferrer"><code>HeaderParser.parsestr()</code> function</a> (same API as Parser but doesn't worry about the email's body) and the <a href="http://docs.python.org/library/email.util.html#email.utils.parseaddr" rel="nofollow noreferrer"><code>parseaddr()</code> function</a>. <pre><code>>>> from email.parser import HeaderParser >>> from email.utils import parseaddr >>> hp = HeaderParser() >>> response = [('1 (BODY[HEADER.FIELDS (MESSAGE-ID)] {78}', 'Message-ID: <actualmessageid@mail.mail.gmail.com>\r\n\r\n'), ')'] >>> header_string = response[0][1] >>> header_string 'Message-ID: <actualmessageid@mail.mail.gmail.com>\r\n\r\n' >>> header = hp.parsestr(header_string) >>> header <email.message.Message instance at 0x023A6198> >>> header['message-id'] '<actualmessageid@mail.mail.gmail.com>' >>> msg_id = parseaddr(header['message-id']) >>> msg_id ('', 'actualmessageid@mail.mail.gmail.com') >>> msg_id[1] 'actualmessageid@mail.mail.gmail.com' </code></pre> Thus: <pre><code>from email.parser import HeaderParser from email.utils import parseaddr hp = HeaderParser() def get_id(response): header_string = response[0][1] header = hp.parsestr(header_string) return parseaddr(header['message-id'])[1] response = [('1 (BODY[HEADER.FIELDS (MESSAGE-ID)] {78}', 'Message-ID: <actualmessageid@mail.mail.gmail.com>\r\n\r\n'), ')'] print(get_id(response)) </code></pre> returns: <pre>actualmessageid@mail.mail.gmail.com</pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POParsing Message-ID header returned by imaplib
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USphobie
UserOwnerUserId
1. USAcorn
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POParsing Message-ID header returned by imaplib
 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
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.