StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
306053
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-11-20T17:03:09.757
FavoriteCount
0
LastActivityDate
2011-11-01T17:43:42.237
LastEditDate
2011-11-01T17:43:42.237
LastEditorUserId
496830
OwnerUserId
37946
ParentId
303562
PostTypeId
2
Score
19
ViewCount
0
LastEditorDisplayName
text
Body
You've all pretty much nailed this already. But it's a little challenging to follow. So let me take a stab at summarizing what you've said... <hr> That difficulties here are that: <ul> <li>We are playing with a temporary <code>ostringstream</code> object, so taking addresses is contra-indicated.</li> <li>Because it's a temporary, we cannot trivially convert to an <code>ostream</code> object through casting.</li> <li>Both the constructor [obviously] and <code>str()</code> are class <code>ostringstream</code> methods. (Yes, we need to use <code>.str()</code>. Using the <code>ostringstream</code> object directly would wind up invoking <code>ios::operator void*()</code>, returning a pointer-like good/bad value and not a string object.)</li> <li><code>operator<<(...)</code> exists as both inherited <code>ostream</code> methods and global functions. In all cases it returns an <code>ostream&</code> reference.</li> <li>The choices here for <code>ostringstream()<<"foo"</code> are the inherited method <code>ostream::operator<<(void* )</code> and the global function <code>operator<<(ostream&,const char* )</code>. The inherited <code>ostream::operator<<(void* )</code> wins out because we can't convert to an <code>ostream</code> object reference to invoke the global function. [Kudos to coppro!]</li> </ul> <hr> So, to pull this off, we need to: <ul> <li>Allocate a temporary <code>ostringstream</code>.</li> <li>Convert it to an <code>ostream</code>.</li> <li>Append data.</li> <li>Convert it back to an <code>ostringstream</code>.</li> <li>And invoke <code>str()</code>.</li> </ul> <hr> Allocating: <code>ostringstream()</code>. Converting: There are several choices. Others have suggested: <ul> <li><code>ostringstream() << std::string() // Kudos to *David Norman*</code></li> <li><code>ostringstream() << std::dec // Kudos to *cadabra*</code></li> </ul> Or we could use: <ul> <li><code>ostringstream() . seekp( 0, ios_base::cur )</code></li> <li><code>ostringstream() . write( "", 0 )</code></li> <li><code>ostringstream() . flush()</code></li> <li><code>ostringstream() << flush</code></li> <li><code>ostringstream() << nounitbuf</code></li> <li><code>ostringstream() << unitbuf</code></li> <li><code>ostringstream() << noshowpos</code></li> <li>Or any other standard manipulator. [<code>#include <iomanip></code>] <a href="http://www.cplusplus.com/reference/iostream/ostream/operator%3C%3C.html" rel="noreferrer">Reference: See "Insert data with format" 1/3 of the way down on this webpage.</a></li> </ul> We cannot use: <ul> <li><strike><code>operator<<( ostringstream(), "" )</code></strike></li> <li><strike><code>(ostream &) ostringstream()</code></strike></li> </ul> Appending: Straightforward now. Converting back: We could just use <code>(ostringstream&)</code>. But a <code>dynamic_cast</code> would be safer. In the unlikely event <code>dynamic_cast</code> returned <code>NULL</code> (it shouldn't), the following <code>.str()</code> will trigger a coredump. Invoking <code>str()</code>: Guess. <hr> Putting it all together. <pre><code>#define FORMAT(ITEMS) \ ( ( dynamic_cast<ostringstream &> ( \ ostringstream() . seekp( 0, ios_base::cur ) << ITEMS ) \ ) . str() ) </code></pre> <hr> References: <ul> <li><a href="http://www.cplusplus.com/reference/iostream/" rel="noreferrer">IOstream Library</a></li> <li><a href="http://www.cplusplus.com/reference/iostream/ostringstream/" rel="noreferrer"><code>ostringstream</code></a></li> <li><a href="http://www.cplusplus.com/reference/iostream/ostream/operator%3C%3C/" rel="noreferrer"><code>ostream::operator<<()</code></a> </li> <li><a href="http://www.cplusplus.com/doc/tutorial/typecasting.html" rel="noreferrer">Type Casting Tutorial</a></li> <li><a href="http://en.wikibooks.org/wiki/C%2B%2B_Programming/Type_Casting" rel="noreferrer">Wiki: Type Casting</a></li> </ul> .
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POC++ format macro / inline ostringstream
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJason Plank
UserOwnerUserId
1. USMr.Ree
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POC++ format macro / inline ostringstream
 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.