Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm not an expert in DDD either , but this is my opinion. This is the situation where the repository patern is applied. Basically, the Domain doesn't know nor care about DAO or anything else rpesistence related. At most knows about the repository inteface (which should be implemented at the infrastructure level).</p> <p>The controller knows about the domain and the repository. The repository encapsulates everything db related, the application knows only about the repository itself (in fact the interface as the actual implementation should be injected). Then within the repository you have DAOs however you see fit. The repository receives and sends back only application/domain objects, nothing related to db acess implementation.</p> <p>In a nutshell, anything db related is part and it's an implementation detail of the repository.</p>
    singulars
    1. This table or related slice is empty.
    1. POMVC with DAO/VO - Which DAO should the Controller talk to?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMikeSW
    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. COYou just create another level (repository) over the DAO, but the question still remains. What should I use? One specific repository that calls other repositories? Or call each repository sequentially (see the example with DAOs in my answer)? Finding all items by named category is an action that no Entity and no repository can provide. For the sake of encapsulation and re-usability it should be encapsulated into something like Service. And not necessarily Service as it defined in DDD context, you can as well call it Action or Command, just some layer that encapsulates common operations.
      singulars
      1. PO
      1. USDmitry Kudryavtsev
    2. COThe repository has avrey clear purpose: to separate the persistence details from the rest of the application. DAO are implementation details. The repository interface is deisgned according to the application usage, you can say somehow that the repository is itself a kind of service used by the app. Finding all items by named category is exactly a method of the repository which will use the necessary DAOs to get those results. Then the repository 'transforms' the persistence objects into application objects (usually via automapping)
      singulars
      1. PO
      1. USMikeSW
    3. COI agree with the roles of the repository as you described it. But lets clarify: Can repository call another repository? What repository should implement the method `FindItemsByCategoryName`, the `CategoryRepository` or `ItemsRepository`?
      singulars
      1. PO
      1. USDmitry Kudryavtsev
 

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