StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1351751
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-08-29T15:55:00.010
FavoriteCount
0
LastActivityDate
2013-06-16T21:49:02.393
LastEditDate
2013-06-16T21:49:02.393
LastEditorUserId
6443
OwnerUserId
6443
ParentId
1351151
PostTypeId
2
Score
12
ViewCount
0
LastEditorDisplayName
text
Body
In general, you can’t. However, you can quite reliably identify UTF-8 files – if a file is valid UTF-8, it’s not very likely that it’s supposed to be any other encoding (except if all the bytes are in the ASCII range, in which case any “extended ASCII” encoding, including UTF-8, will give you the same result). All Unicode encodings also have an optional <a href="http://en.wikipedia.org/wiki/Byte-order_mark" rel="noreferrer">BOM</a> which identifies them. So a reasonable approach would be: <ul> <li>Look for a valid BOM. If there is one, use the appropriate encoding.</li> <li>Otherwise, try to interpret it as UTF-8. You can do this by calling <code>initWithData:data encoding:NSUTF8StringEncoding</code> and checking if the result is non-nil.</li> <li>If that fails, use a default 8-bit encoding, such as <code>-[NSString defaultCStringEncoding]</code> (which provides a locale-appropriate guess).</li> </ul> It is possible to try to improve the guess in the last step by trying various different encodings and choosing the one which has fewest sequences of letters with junk in the middle, where “junk” is any character that’s not a letter, space or common punctuation mark. This would significantly increase complexity while not actually being reliable. In short, to be able to handle all available encodings you need to do what TextEdit does: shunt the decision over to the user. Oh, one more thing: as of 10.5, the encoding is often stored with a file in the undocumented com.apple.TextEncoding extended attribute. If you open a file with <code>+[NSString stringWithContentsOfFile:]</code> or similar, this will automatically be used if present.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGuess encoding when creating an NSString from NSData
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJens Ayton
UserOwnerUserId
1. USJens Ayton
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POGuess encoding when creating an NSString from NSData
 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.