StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9927369
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-03-29T14:25:41.420
FavoriteCount
0
LastActivityDate
2012-03-29T14:25:41.420
LastEditDate
LastEditorUserId
0
OwnerUserId
1236280
ParentId
8021579
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
My Answer involves not using DQL and instead creating a NestedSetManager which has access to your DBAL connection so you can use SQL. I never felt like the ORM's did a good job with NestedSets query logic. With a <code>NestedSetManager</code>, you can then write a bunch of clean methods and it's really simple because all these queries are well documented. See <a href="http://mikehillyer.com/articles/managing-hierarchical-data-in-mysql/" rel="nofollow">this link</a>. Some of the method in my NestedSetManager are: <pre><code>setNode(); setRoot(); loadNestedSet(); moveNodeUp(); modeNodeDown(); getRootNode(); addNodeSibling(); getNodesByDepth(); getParents(); getNodePath(); childExists(); addChildToNode(); renameNode(); deleteNode(); // And many more </code></pre> You can have a ball and create a lot of create NestedSet functionality if you're not tied down by an ORM's somewhat complex functionality. Also -- Symfony2 makes all this really really easy. You create your NestedSetManager class file and reference it in your Services.yml and pass in your Dbal connection. Mine looks like this: <pre><code>services: manager.nestedset: class: Acme\CoreBundle\Manager\NestedSetManager arguments: [ @database_connection ] </code></pre> you can then access your nestedsets with: <pre><code>$path = $this->get('manager.nestedset')->setNode(4)->getNodePath(); // in your controller </code></pre> Moral of the story, ORM/NestedSets drove me bonkers and this solution work really well. If you're being forced to use DQL and have no other options, this answer probably wont be acceptable.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POLazy Loading with Doctrine2 and Symfony2 using DQL
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJustinP
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
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.