Databases
StackOverflow2013
Postsdbo
POShould the business logic be separate from the model?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POShould the business logic be separate from the model?
    primarykey
    data
    text
    <p>We're working on a fairly code-heavy PHP5 project, and in the last week I worked on a PoC of a RESTful API. We are separating Model Classes from Business Classes.</p> <p>Trying to implement CRUD functionality, I discovered, that implementing CRUD against the Models directly would be pretty straight-forward while implementing it against the Business Logic isn't, since its functionality is specific to the currently existing Views and its interface doesn't provide the general data access model I need for implementing the API.</p> <p>Thinking about this, the following questions came to my mind:</p> <ul> <li><p>What is the best way to interact with the data, keeping the flexibility of the model <em>and</em> keeping the functionality the model doesn't care about at the moment (like sending a mail with an activation link when changing the email address)?</p></li> <li><p>Working a lot with django previously, where most of the business logic is implemented in the model, why should you keep the business logic separate anyway? Do you have any real-life examples? What problems does this solve, if any?</p></li> </ul> <p>Some possible solutions came to my mind, too:</p> <ul> <li>Putting the whole business logic into the model. Checking which fields changed after / before calling the save method.</li> <li>Using the observer pattern to notify the business objects of changes in the model and interact with the models directly.</li> </ul> <p>What are the pros and cons in your opinion, what would you do?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. UShakre
    1. USstefreak
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POShould the business logic be separate from the model?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POShould the business logic be separate from the model?
      1. USMuqito
      1. VTFavorite
    3. VO
      singulars
      1. POShould the business logic be separate from the model?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIn MVC, the Model is not the database (or some other persistence). The Model in MVC is where significant algorithms for solving the business problem live. It just so happens the Model typically communicates with the database usually @Luc Franken writes via a Data Access Layer (i.e. Gateway, Data Access, Active Record and/or Data Transfer objects).
      singulars
      1. POShould the business logic be separate from the model?
      1. USorangepips
 

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