StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12508880
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-09-20T08:34:01.990
FavoriteCount
0
LastActivityDate
2012-09-20T08:34:01.990
LastEditDate
LastEditorUserId
0
OwnerUserId
316644
ParentId
12507986
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
<p>Here's a way to do that:</p> <pre><code>Date <- c("2009-05-1 10:00:00","2009-05-1 10:05:00","2009-05-1 10:10:00","2009-05-1 10:15:00","2009-05-1 10:20:00","2009-05-1 10:25:00") Dates <- strptime(Date, "%Y-%m-%d %H:%M:%S") DF <- data.frame(Dates,X=1:6, Y=1:6) DF2 <- merge(DF,data.frame(Dates=DF$Dates - 5 * 60, YNext=DF$Y),by='Dates',all.x=T,all.y=F) DF3 <- merge(DF2,data.frame(Dates=seq(from=min(DF2$Dates),to=max(DF2$Dates),by='1 min')),by='Dates',all=TRUE) tmpFun <- function(d){ d$X <- na.omit(d$X)[1] d$Y <- ifelse(is.na(d$Y),(na.omit(d$Y)[1] + na.omit(d$YNext)[1]) / 2,d$Y) return(d) } DF4 <- do.call(rbind,by(DF3,INDICES=(as.POSIXlt(DF3$Dates)$min %/% 5),FUN=tmpFun)) # "beautify" the data.frame (set the row names, and remove the YNext column) row.names(DF4) <- 1:nrow(DF4) DF4$YNext <- NULL </code></pre> <p>Result:</p> <pre><code>> DF4 Dates X Y 1 2009-05-01 10:00:00 1 1.0 2 2009-05-01 10:01:00 1 1.5 3 2009-05-01 10:02:00 1 1.5 4 2009-05-01 10:03:00 1 1.5 5 2009-05-01 10:04:00 1 1.5 6 2009-05-01 10:05:00 2 2.0 7 2009-05-01 10:06:00 2 2.5 8 2009-05-01 10:07:00 2 2.5 9 2009-05-01 10:08:00 2 2.5 10 2009-05-01 10:09:00 2 2.5 11 2009-05-01 10:10:00 3 3.0 12 2009-05-01 10:11:00 3 3.5 13 2009-05-01 10:12:00 3 3.5 14 2009-05-01 10:13:00 3 3.5 15 2009-05-01 10:14:00 3 3.5 16 2009-05-01 10:15:00 4 4.0 17 2009-05-01 10:16:00 4 4.5 18 2009-05-01 10:17:00 4 4.5 19 2009-05-01 10:18:00 4 4.5 20 2009-05-01 10:19:00 4 4.5 21 2009-05-01 10:20:00 5 5.0 22 2009-05-01 10:21:00 5 5.5 23 2009-05-01 10:22:00 5 5.5 24 2009-05-01 10:23:00 5 5.5 25 2009-05-01 10:24:00 5 5.5 26 2009-05-01 10:25:00 6 6.0 </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAdd and fill in rows based on data above/below
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USdigEmAll
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAdd and fill in rows based on data above/below
  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
  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.