StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14165818
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-04T22:11:18.240
FavoriteCount
0
LastActivityDate
2013-01-04T22:19:57.233
LastEditDate
2013-01-04T22:19:57.233
LastEditorUserId
958580
OwnerUserId
958580
ParentId
11050918
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I don't know if you still want an answer but here is my bash... I can see the following problems in your code are as follows : <ul> <li>You've asigned resultsName multiple times to multiple items, as a Dict could eventually be returned you must either add '*' to each occurence of resultsName or drop it from a number of elements. I'll assume you are after the content and not the tags and drop their names. FYI, The shortcut for setting parser.resultsName(name) is parser(name).</li> <li>Setting the resultsname to 'Contents' for everything is also a bad idea as we would loose information already available to us. Rather name CONTENTS by it's corresponding TAG.</li> <li>You are also making multiple items Optional within the0 ZeroOrMore, they are already 'optional' through the ZeroOrMore, so let's allow them to be variations using the '^' operator as there is no predefined sequence ie. pc tags could precede mul tags or vice versa. It seems reasonable to allow any combintation and collect these as we go by. </li> <li>As we also have to deal with multiples of a given tag we append '*' to the CONTENTS' resultsName so that we can collect the results into lists. </li> </ul> First we create a function to create set of opening and closing tags, your DumbTagCreator is now called tagset : <pre><code>from pyparsing import * def tagset(str, keywords = False): if keywords : return [Group(Literal('<') + Keyword(str) + Literal('>')).suppress(), Group(Literal('</') + Keyword(str) + Literal('/>')).suppress()] else : return [Group(Literal('<') + Literal(str) + Literal('>')).suppress(), Group(Literal('</') + Literal(str) + Literal('>')).suppress()] </code></pre> Next we create the parser which will parse <code><tag\>CONTENT</tag></code>, where CONTENT is the content we have an interest in, to return a dict so that we have <code>{'pc' : CONTENT, 'MW' : CONTENT, ...}</code>: <pre><code>tagDict = {name : (tagset(name)) for name in ['pc','MW','L','mul','mat']} parser = None for name, tags in tagDict.iteritems() : if parser : parser = parser ^ (tags[0] + SkipTo(tags[1])(name) + tags[1]) else : parser = (tags[0] + SkipTo(tags[1])(name) + tags[1]) # If you have added the </mul> tag deliberately... parser = Optional(Literal('<mul/>')) + ZeroOrMore(parser) # If you have added the </mul> tag by acccident... parser = ZeroOrMore(parser) </code></pre> and finally we test : <pre><code>test = ['<L>1.1</L>', '<pc>Page1,1</pc> <pc>Page1,2</pc> <MW>000001</MW> <L>1.1</L>', '<mul/><MW>000003</MW><pc>1,1</pc><L>3.1</L>', '<mul/> <MW>000003</MW> <pc>1,1</pc> <L>3.1</L> '] for item in test : print {key:val.asList() for key,val in parser.parseString(item).asDict().iteritems()} </code></pre> which should produce, assuming you want a dict of lists : <pre><code>{'L': ['1.1']} {'pc': ['Page1,1', 'Page1,2'], 'MW': ['000001'], 'L': ['1.1']} {'pc': ['1,1'], 'MW': ['000003'], 'L': ['3.1']} {'pc': ['1,1'], 'MW': ['000003'], 'L': ['3.1']} </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPyparsing: a list of optional elements: weird issue with Optional, Each, and ordering of parser elements
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCarel
UserOwnerUserId
1. USCarel
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. This table or related slice is empty.
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.