StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8193783
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-11-19T11:37:21.940
FavoriteCount
0
LastActivityDate
2011-11-19T11:37:21.940
LastEditDate
LastEditorUserId
0
OwnerUserId
743214
ParentId
8182972
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Besides the obvious check for <code>argc != 2</code> I couldn't help fixing some of the worse code and the obvious error: <pre><code>#include <iostream> #include <fstream> #include <string> using namespace std; int main (int argc, char* argv[]) { if (argc != 2) { cout << "ERROR. Invalid number of arguments\n"; return 1; } ifstream infile(argv[1]); if (!infile) // covers a miss spelling of a fail name { cout << "ERROR. Did you make a mistake in the Spelling of the File\n"; return 1; } string STRING; while(getline(infile, STRING)) cout << STRING << '\n'; // Prints out file line return 0; } </code></pre> You don't need to call <code>ifstream::open</code>, just use the constructor, likewise don't you need to declare <code>STRING</code> so early and neither to initialize it to the file name, since you don't use it. Don't forget, this is not C, you don't need a whole mess of declarations at the beginning of each function. Second, checking for the flags of a stream is often a bad idea, just check for <code>!infile</code> to find any errors. But the real error is in checking for <code>infile.eof</code> in the while condition, since it only gets set once <code>getline</code> has tryed to read over the end of the file, so you would actually print one (probably empty) line too much. Just check for <code>getline</code>'s return value to find any errors or the end of file. And don't add the newline onto the string when outputting, just put it out after the string. And last but not least, no need for <code>infile.close</code>, since the destructor calls it anyway.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POArgument checking
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USChristian Rau
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. 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
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.