Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Quoting <a href="http://en.wikipedia.org/wiki/Composite_pattern" rel="nofollow">wikipedia:</a></p> <blockquote> <p>Composite pattern can be used when clients should ignore the difference between compositions of objects and individual objects.</p> </blockquote> <p>Since the idea is to treat a group of objects as a single one (of the same type), usually the composite object iterates through its group (of children) in order to propagate the same behavior. Keeping a list of children in the parent makes more sense from this aspect.</p> <p><strong>Update</strong>: I misunderstood your question. Let me try again: Usually the composite object keeps reference to its children, for the reason above. The parent link might (or not) be excess. Why do you want to keep a reference to the parent? Is there a shared state between the children?</p> <p><strong>Update 2</strong>: Allright, the parent link should be there. In this case, both ways you mention are functionally equivalent and this is essentially an API design question. A TDD-ish way of thinking could help you here. For example, since the scenegraph is essentially a tree, a simple scenario can be creating the first nodes. This is how you'd do it in both versions (as I understand):</p> <pre><code>// First way: // Shorter but still readable. Parent relationship established at construction, so you can count on that the parent property is always at its final state. Composite root = new Composite(null); Composite child = new Composite(root); // Second way: // Has an extra statement but more explicit. Also slightly more flexible since the parent relationship can be established _after_ construction. Composite root = new Composite(); Composite child = new Composite(); root.addChild(child); </code></pre> <p>Maybe re-parenting a node might be another interesting test, if you have that kind of a requirement. Determining your most important operations and designing for them will shape the API in the most appropriate way.</p>
    singulars
    1. This table or related slice is empty.
    1. POComposite design pattern parenting components
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UShenginy
    1. UShenginy
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYes I know... but I've forgot to add the child to the list of children in the constructor... will fix it in a second.
      singulars
      1. PO
      1. USspectre
    2. COActually I didn't mean that. But now I see that I misunderstood your question.
      singulars
      1. PO
      1. UShenginy
    3. COThere might be many reasons to preserve the link to parent element. In my case, I'm developing GUI library and 3D scene graph. The child elements of GUI have to know what's parent clipping area so they dont go out of parent bounds. For the scenegraph - it's for creating nested transforms - when parent object rotates - the child object rotates with the parent so the parent current tranformation has to be known.
      singulars
      1. PO
      1. USspectre
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload