StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
235336
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
8
CommunityOwnedDate
CreationDate
2008-10-24T21:32:42.223
FavoriteCount
0
LastActivityDate
2008-10-24T22:20:44.857
LastEditDate
2008-10-24T22:20:44.857
LastEditorUserId
14089
OwnerUserId
14089
ParentId
235326
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
paercebal
text
Body
<h2>The "optimized way"</h2> If we ignore the "premature optimization is the root of all evil", the standard way is to add a comparator, which is easy to write: <pre><code>struct MyCharComparator { bool operator()(const char * A, const char * B) const { return (strcmp(A, B) < 0) ; } } ; </code></pre> To use with a: <pre><code>std::set<const char *, MyCharComparator> </code></pre> <h2>The standard way</h2> Use a: <pre><code>std::set<std::string> </code></pre> It will work even if you put a static const char * inside (because std::string, unlike const char *, is comparable by its contents). Of course, if you need to extract the data, you'll have to extract the data through std::string.c_str(). In the other hand, , but as it is a set, I guess you only want to know if "AAA" is in the set, not extract the value "AAA" of "AAA". Note: I did read about "Please do not suggest creating std::strings", but then, you asked the "standard" way... <h2>The "never do it" way</h2> I noted the following comment after my answer: <blockquote> <blockquote> Please do not suggest creating std::strings - it is a waste of time and space. The strings are static, so they can be compared for (in)equality based on their address. </blockquote> </blockquote> This smells of C (use of the deprecated "static" keyword, probable premature optimization used for std::string bashing, and string comparison through their addresses). Anyway, you don't want to to compare your strings through their address. Because I guess the last thing you want is to have a set containing: <pre><code>{ "AAA", "AAA", "AAA" } </code></pre> Of course, if you only use the same global variables to contain the string, this is another story. In this case, I suggest: <pre><code>std::set<const char *> </code></pre> Of course, it won't work if you compare strings with the same contents but different variables/addresses. And, of course, it won't work with static const char * strings if those strings are defined in a header. But this is another story.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSimplest, safest way of holding a bunch of const char* in a set?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USpaercebal
UserOwnerUserId
1. USpaercebal
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
 VTDownMod
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

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.