Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The term is "object orientation" wherein you decompose large complex problems into smaller problems by defining classes of objects each of which encapsulates a small part of the problem. The way objects interact is by message passing and objects find other objects to pass messages to by starting with the objects they contain.</p> <p>The larger and more complex the problem, the more work you have to do to decompose it into manageable pieces, so the more layers of objects you get. Sometimes small simple problems are decomposed badly into large numbers of objects, but that doesn't make object orientation itself an anti-pattern.</p> <hr> <blockquote> <p>the main problem is simply that the data objects grow too large through nesting as well as including irrelevent data. Example: You're sorting birds and rather than a simple bird object you receive an object bird, containing feathers, beak, possibleParasites, air, possibleHousesNestsCanBeIn, and foodTypes, food types contains fruit, insects, worms, seeds, seeds contains oak, elm, thistle, possibleAnimalsThatCanEatSeeds etc etc –</p> </blockquote> <p>The <a href="http://blogs.msdn.com/b/ebattalio/archive/2006/11/16/anti-pattern-kitchen-sink-maps.aspx" rel="nofollow">Everything but the kitchen-sink map</a> anti-pattern is probably the closest fit.</p> <blockquote> <p>Given a complex process with many complex rules, everything (business logic, related and unrelated procedures, etc) is shoved into the map.</p> </blockquote> <p>The best way to solve this is with a filtering operation where you specify a strongly typed interface like <code>interface BirdList extends Iterable&lt;Bird&gt; {}</code> and the query system provides an implementation of that backed by just enough data to support that interface.</p> <p>Your API could provide a number of different interfaces like <code>BirdList</code> and <code>BirdFeedingHabitMap</code>, <code>BirdNestingHabitMap</code>, etc. Clients can come up with a list of interfaces they need and the query system analyzes them, fetches the data, and uses <a href="http://docs.oracle.com/javase/1.3/docs/guide/reflection/proxy.html" rel="nofollow">proxy classes</a> to assemble an implementation class that exposes the query results in a type-safe way.</p>
    singulars
    1. This table or related slice is empty.
    1. POJava antipattern name? Objects containing objects containing... etc
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMike Samuel
    1. USMike Samuel
    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
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CONaturally, I'm not arguing with that, I'm speaking about when you have objects, specifically data objects nested to the nth degree causing bloat of data and trouble with being able to access the correct data or even know what data is included upon retrieving an object
      singulars
      1. PO
      1. USFooBar
    2. CO@FooBar, please see my edit
      singulars
      1. PO
      1. USMike Samuel
    3. COWhile this can be a problem it is not the main problem, the main problem is simply that the data objects grow too large through nesting as well as including irrelevent data. Example: You're sorting birds and rather than a simple bird object you receive an object bird, containing feathers, beak, possibleParasites, air, possibleHousesNestsCanBeIn, and foodTypes, food types contains fruit, insects, worms, seeds, seeds contains oak, elm, thistle, possibleAnimalsThatCanEatSeeds etc etc
      singulars
      1. PO
      1. USFooBar
 

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