Re: IDDD - Repository add vs save
Brian Sayatovic <[email protected]>
| Newsgroups | gmane.comp.programming.domain-driven-design |
|---|---|
| Message-ID | <CANXx7X29g4T-wKCDBCj8=UihbzonuQ1NQ2yU3kOUtKbKwh771g@mail.gmail.com> |
That is what my enterprise does. We implemented the Nilsson Workspace pattern ourselves, on top of NHibernate. We do have to tell repositories about *new* entities, but when we retrieve and manipulate existing entities, there is no need to tell the repository. They were fetched under a unit of work and therefore will be committed with the unit of work implicitly. On Thu, Sep 26, 2013 at 9:50 PM, Alistair Bush <[email protected]>wrote: > ** > > > As they are implemented as a Unit of Work. Which basically allows you to > make a number of changes and then save them all in a single operation. > > There is nothing stopping you from having a repository interface without > the save method and just 'in the background' call save. > -- Regards, Brian.