StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10778470
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-05-28T01:22:21.790
FavoriteCount
0
LastActivityDate
2012-05-28T01:22:21.790
LastEditDate
LastEditorUserId
0
OwnerUserId
1144035
ParentId
10773568
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
The correlated subqueries, without an index, are going to do a cross join anyway. So, another way of expressing the query is: <pre><code>select rp.*, min(abs(rp.t - rq.t)) from rp cross join rq group by <rp.*> -- <== need to replace with all columns </code></pre> There is another method, which is a bit more complicated. This requires using the cumulative sum. Here is the idea. Combine all the rp and rq values together. Now, enumerate them by the closest rp value. That is, create a flag for rp and take the cumulative sum. As a result, all the rq values between two rp values have the same rp index. The closest value to a given rq value has an rp index the same as the rq value or one more. Calculating the the rq_index uses the cumulative sum. The following query puts this together: <pre><code>with rqi as (select t.*, sum(isRQ) over (order by t) as rq_index from (select rq.t, 0 as isRP, <NULL for each rp column> from rq union all select rq.t, 1 as isRP, rp.* from rp ) t ) t select rp.*, (case when abs(rqprev.t - rp.t) < abs(rqnext.t - rp.t) then abs(rqprev.t - rp.t) else abs(rqnext.t - rp.t) end) as closest_value from (select * from t where isRP = 0 ) rp join (select * from t where isRP = 1 ) rqprev on rp.rp_index = rqprev.rp_index join (select * from t where isRP = 1 ) rqnext on rp.rp_index+1 = rpnext.rq_index </code></pre> The advantage of this approach is that there is no cross join and no correlated subqueries.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POERROR: subquery in FROM cannot refer to other relations of same query level
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USGordon Linoff
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. This table or related slice is empty.
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.