Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>DDD is a way of thinking while designing a software that starts with modelling the domain. As the <a href="http://domaindrivendesign.org/resources/what_is_ddd" rel="nofollow noreferrer">webpage</a> puts it:</p> <blockquote> <p>Domain-driven design is not a technology or a methodology. It is a way of thinking and a set of priorities, aimed at accelerating software projects that have to deal with complicated domains.</p> </blockquote> <p>One thing that follows naturally out of this design pattern is a layered architecture. As it is said in <a href="http://domaindrivendesign.org/sites/default/files/discussion/PatternSummariesUnderCreativeCommons.doc" rel="nofollow noreferrer">DDD Pattern Summaries</a></p> <blockquote> <p>Partition a complex program into LAYERS. Develop a design within each LAYER that is cohesive and that depends only on the layers below. Follow standard architectural patterns to provide loose coupling to the layers above. Concentrate all the code related to the domain model in one layer and isolate it from the user interface, application, and infrastructure code. The domain objects, free of the responsibility of displaying themselves, storing themselves, managing application tasks, and so forth, can be focused on expressing the domain model. This allows a model to evolve to be rich enough and clear enough to capture essential business knowledge and put it to work.</p> </blockquote> <p>Whether you need to have display objects to do that? That is just one way of implementing this, but might not even be the best to provide loose coupling. As for an example: maybe the view layer is but a webbrowser and xlt files to visualize xml files emmitted by the business layer? If anybody has more fitting examples, please add them. My point is that DDD stresses a layered architecture, but does not limit this to one possible solution.</p>
    singulars
    1. This table or related slice is empty.
    1. POIn Domain-Driven Design, can you use your domain entities in your UI?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRalph M. Rickenbach
    1. USRalph M. Rickenbach
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIn Domain-Driven Design, can you use your domain entities in your UI?
      singulars
      1. PTQuestion
    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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COExcellent answer, bravo
      singulars
      1. PO
      1. USMark Rogers
 

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