Databases
StackOverflow2013
Postsdbo
POIn the MVC pattern, what goes in the model and what goes in the view?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIn the MVC pattern, what goes in the model and what goes in the view?
    primarykey
    data
    text
    <p>I'm using the <a href="https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller" rel="nofollow noreferrer">MVC</a> pattern to design some data analysis software (in <a href="http://en.wikipedia.org/wiki/Python_%28programming_language%29" rel="nofollow noreferrer">Python</a>). I'm not sure whether some functions should go in the model or the controller.</p> <p>The way I've designed it, the user supplies the program a configuration file which contains the parameters for analysis. The program parses this file to find out what data files to look at and what kinds of calculations to do.</p> <ul> <li>Should the function(s) that do this configuration file parsing be in the model or the controller?</li> <li>Is there a standard way to organize things in Python when using MVC? I've made the model, controller, and view into separate classes. The controller class contains instances of the model and view classes.</li> <li>What kind of communication should there be between the model and the view? The way I'm structuring things is so that the controller takes stuff from the model and passes it to the view. The two only communicate through the controller.</li> </ul>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPeter Mortensen
    1. USpealco
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

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