StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8306427
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-11-29T05:45:00.870
FavoriteCount
0
LastActivityDate
2011-11-29T05:54:49.273
LastEditDate
2011-11-29T05:54:49.273
LastEditorUserId
396551
OwnerUserId
396551
ParentId
8306267
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Suppose <code>node1->next == node2 && node2->prev == node1</code>. Now let's trace: <pre><code>if(node1->next!=NULL) { node1->next->prev=node2; } </code></pre> Now <code>node2->prev</code> points to <code>node2</code> itself! <pre><code>if(node2->prev!=NULL) { node2->prev->next=node1; } </code></pre> Now <code>node2->next</code> points to <code>node1</code>, which is ok for now. Recall that <code>node1->next</code> still points to <code>node2</code>, and <code>node2->next</code> points to <code>node1</code>. <pre><code>tmp=node1->next; // == node2 node1->next=node2->next; // == node1 (!) node2->next=tmp; // == node2 </code></pre> So we have <code>node1->next</code> pointing to <code>node1</code>, and <code>node2->next</code> to <code>node2</code>. Clearly wrong. Recall that node2->prev points to <code>node2</code>, although <code>node1->prev</code> is correct. <pre><code>tmp=node1->prev; // correct node1->prev=node2->prev; // == node2 node2->prev=tmp; // correct </code></pre> So <code>node1->prev</code> points to <code>node2</code>, which is correct. But <code>node1->next</code> and <code>node2->next</code> are still wrong! <hr> How to solve this? It's not a one-liner to solve, as there are a couple special cases. Maybe detect the special case I described and have separate code for it (and don't forget about that other special case). Writing that code is left as an exercise to the reader ;)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POdebug help - swap 2 nodes of double link list
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USSjoerd
UserOwnerUserId
1. USSjoerd
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.