StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12866840
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-10-12T20:44:28.980
FavoriteCount
0
LastActivityDate
2012-10-12T20:44:28.980
LastEditDate
LastEditorUserId
0
OwnerUserId
485185
ParentId
12300933
PostTypeId
2
Score
8
ViewCount
0
LastEditorDisplayName
text
Body
Marc Cohen seems to be right, I think something is broken. However I managed to pass authentication, here is how: Download the <code>googlepredictionapi_0.12.tar.gz</code> and extract it inside a temporary folder. Then open <code>googlepredictionapi/R/prediction_api_init.R</code> inside an Editor and remove the lines <pre><code>myEmail <- "" myPassword <- "" myAPIkey <- "" </code></pre> Afterwards repackage the source files and load them in R: <pre><code>tar czf googlepredictionapi.mod.tar.gz googlepredictionapi R remove.packages("googlepredictionapi") </code></pre> Now you should be able to follow the steps in [1] <a href="http://code.google.com/p/r-google-prediction-api-v12/">http://code.google.com/p/r-google-prediction-api-v12/</a>. However instead of calling <pre><code>install.packages("googlepredictionapi_0.12.tar.gz", repos=NULL, type="source") </code></pre> you need to call <pre><code>install.packages("googlepredictionapi.mod.tar.gz", repos=NULL, type="source") </code></pre> Following the steps, at some point a file <code>$HOME/.auth-token</code> should be generated. (You can even explicitly trigger this by calling explicitely: <code>PredictionApiUtilGetAuth(verbose=TRUE)</code>, <code>myEmail</code> and <code>myPassword</code> must be set beforehands.) For some reason the global variables that are manually set in [1] have been shadowed by the removed lines above. The same is actually true for the verbose option which you can pass to most API function calls as extra option <code>..., verbose=TRUE)</code>. Hope this helps.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGoogle Prediction using R
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USPhilip
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
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.