StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19097159
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2013-09-30T14:44:56.607
FavoriteCount
0
LastActivityDate
2016-10-20T14:57:23.117
LastEditDate
2016-10-20T14:57:23.117
LastEditorUserId
601386
OwnerUserId
601386
ParentId
3834791
PostTypeId
2
Score
67
ViewCount
0
LastEditorDisplayName
text
Body
<h2>This also arises if you compare recursive objects using <code>==</code> instead of <code>===</code></h2> If you need to compare actual object instances always use the strict comparison operator <code>===</code> as it only compares if the objects refer to the same instance of the same class. Short explanation: If you compare objects using <code>$object == $objectToCompareWith</code>, PHP is comparing every attribute and value of the first object with the second. This comparison is recursive over objects which are properties of the objects being compared. That means that if both objects share an attribute with an object as its value, PHP does the same <code>==</code> comparison between those attribute objects. Now as soon as on of those attribute objects is recursive (e.g. a self referencing object) the comparison recurses down too until the maximum nesting level is reached. As stated in the comments by Josh Stuart and mazatwork, strict comparison can be forced when using array functions like <code>in_array()</code> and <code>array_search()</code> by setting their respective <code>$strict</code> parameter to <code>true</code>. <a href="http://www.richardlord.net/blog/php-nesting-level-too-deep-recursive-dependency" rel="noreferrer">Richard Lord: "Nesting level too deep – recursive dependency?"</a> <a href="http://www.php.net/manual/en/language.oop5.object-comparison.php" rel="noreferrer">PHP Manual: "Comparing Objects"</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFatal error: Nesting level too deep - recursive dependency?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USflu
UserOwnerUserId
1. USflu
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. COflu - you're my hero of the day. So obvious once you read it... Thanks!
 singulars
 PostPostId
 PO
 UserUserId
 USkander

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.