Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The best and easiest way for this is to use Doctrine2. Maybe the first hours will be hard, but once you master the Doctrine2 all such relationships and aggregate are piece of cake. </p> <p>You can find plenty of information about PHP &amp; DDD or Doctrine2 on <a href="http://giorgiosironi.blogspot.com/" rel="nofollow">http://giorgiosironi.blogspot.com/</a> or just by googling. </p> <p>RE: Validation - considering the Single Responsibility Principle we use Validation objects. Validation can be complex and may require other repositories or entities so it is better to keep it apart from the actual entity - subject of the validation to avoid creation of bloated objects. You can either use visitor or specification design pattern. </p> <p>There is plenty other posts here regarding those topics - try to use the above keywords.</p>
    singulars
    1. This table or related slice is empty.
    1. PODDD - Entity creation and validation responsibility
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USTomas Dermisek
    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. COI used doctrine back then, didn't really liked it, it was big and heavy. However it was pre Doctrine2, I might give Doctrine a shot again. However I'm still more interested in the proper way of doing things than finding a ready solution. As for validation, thanks for bringing the SRP! I forgot about it at all and was not sure if I should insert another layer of Validation, now I'm sure I need :)
      singulars
      1. PO
      1. USDmitry Kudryavtsev
    2. CODoctrine was based on Active Record pattern, Doctrine2 is exactly what you need for easier implementation of DDD. As I wrote on another similar post - home-built solutions usually end up as maintenance nightmare and Aggregate Roots become very manual. Usually every AR is done different way based which developer made it. Been there, trust me, you don't want to go that way ...
      singulars
      1. PO
      1. USTomas Dermisek
    3. COI have "reinvent-the-wheel" syndrome. If I were asked to implement DDD at my work place with tight schedule I'd probably go with Doctrine. Since my question was raised from my personal project, in which I don't have strict dead lines, I prefer to learn as much as possible by implementing this stuff. I have a nice solution ATM but I'm afraid it will break as soon as Ill try to complicate it, so I'm considering Doctrine. Also AFAIK Doctrine does not support non DB storage (i.e. file based or noSQL databases), this might be an issue for the future (I'm sure writing a driver is not a problem).
      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