StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3895901
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-10-09T06:10:18.437
FavoriteCount
0
LastActivityDate
2010-10-12T16:47:35.997
LastEditDate
2010-10-12T16:47:35.997
LastEditorUserId
147019
OwnerUserId
147019
ParentId
3895874
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
FIRST APPROACH - Well, using regular expression(s) you could do like so - <pre><code>import re re.sub('g+', 'g', 'omgggg') re.sub('l+', 'l', 'lollll') </code></pre> etc. Let me point out that using regular expressions is a very fragile & basic approach to dealing with this problem. You could so easily get strings from users which will break the above regular expressions. What I am trying to say is that this approach requires lot of maintenance in terms of observing the patterns of mistakes the users make & then creating case specific regular expressions for them. SECOND APPROACH - Instead have you considered using <code>difflib</code> module? It's a module with helpers for computing deltas between objects. Of particular importance here for you is <code>SequenceMatcher</code>. To paraphrase from <a href="http://docs.python.org/library/difflib.html" rel="nofollow">official documentation</a>- <blockquote> SequenceMatcher is a flexible class for comparing pairs of sequences of any type, so long as the sequence elements are hashable. SequenceMatcher tries to compute a "human-friendly diff" between two sequences. The fundamental notion is the longest contiguous & junk-free matching subsequence. </blockquote> <pre><code>import difflib as dl x = dl.SequenceMatcher(lambda x : x == ' ', "omg", "omgggg") y = dl.SequenceMatcher(lambda x : x == ' ', "omgggg","omg") avg = (x.ratio()+y.ratio())/2.0 if avg>= 0.6: print 'Match!' else: print 'Sorry!' </code></pre> According to documentation, any ratio() over 0.6 is a close match. You might need to explore tweak the ratio for your data needs. If you need more stricter matching I found any value over 0.8 serves well.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORegex to match 'lol' to 'lolllll' and 'omg' to 'omggg', etc
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USSrikar Appalaraju
UserOwnerUserId
1. USSrikar Appalaraju
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORegex to match 'lol' to 'lolllll' and 'omg' to 'omggg', etc
 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
 VTUpMod
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.