StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2516143
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-03-25T14:04:49.367
FavoriteCount
0
LastActivityDate
2010-03-25T14:04:49.367
LastEditDate
LastEditorUserId
0
OwnerUserId
299572
ParentId
2515570
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
<p>The X12 protocol standard allows the specification of element and component separators in the header, so anything that hard-codes the "|" and ">" characters could eventually break. Since the standard mandates that the characters used as separators (and segment terminators, e.g., "~") cannot appear within the data (there is no escape sequence to allow them to be embedded), parsing the syntax is very simple. Maybe you're already doing something similar to this, but for readability...</p> <pre><code>// The original segment string (without segment terminator): string segment = "PLB|1902841224|20100228|49>KC15X078001104|.08"; // Parse the segment into elements, then the fourth element // into components (bounds checking is omitted for brevity): var elements = segment.Split('|'); var components = elements[3].Split('>'); // If the first component is the bad value, replace it with // the correct value (again, not checking bounds): if (components[0] == "49") components[0] = "CS"; // Reassemble the segment by joining the components into // the fourth element, then the elements back into the // segment string: elements[3] = string.Join(">", components); segment = string.Join("|", elements); </code></pre> <p>Obviously more verbose than a single regular expression but parsing X12 files is as easy as splitting strings on a single character. Except for the fixed length header (which defines the delimiters), an entire transaction set can be parsed with Split:</p> <pre><code>// Starting with a string that contains the entire 835 transaction set: var segments = transactionSet.Split('~'); var segmentElements = segments.Select(s => s.Split('|')).ToArray(); // segmentElements contains an array of element arrays, // each composite element can be split further into components as shown earlier </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORegex: replace inner string
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UStames
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. COThat's pretty close to what I'm doing now. I'm just hoping there's a better way to do it...
  singulars
  PostPostId
  PO
  UserUserId
  USAllenG

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.