Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I've built my own framework in the past too so I know what you're going through. I've heard the saying "build fat models" and I agree with that -- as long as the main goal is to return data. I considered the controller to be "The Overlord" as it manipulated data and directed where it should go.</p> <p>For a login controller i might create something it like...</p> <p>Post URI: <a href="http://example.com/login/authenticate" rel="nofollow">http://example.com/login/authenticate</a></p> <pre><code>LoginController extends ParentController { public function authenticate() { $credential_model = $this-&gt;getModel('credentials'); // Obviously you should sanitize the $_POST values. $is_valid = $credential_model-&gt;isValid($_POST['user'], $_POST['email']); $view = $is_valid ? 'login_fail.php' : 'login_success.php'; $data = array(); $data['a'] = $a; // .. more vars $this-&gt;view-&gt;render($view, $data); } } </code></pre> <p>In my opinion data should always flow from the model -> controller -> view as it makes the most sense (data, manipulation, output). The View should only have access to what it has been given by the controller.</p> <p>As for this...</p> <blockquote> <p>Then if I'm dynamically calling my controller, how can I persist the data unique to the controller necessary to render the view?</p> </blockquote> <p>Well I would imagine you're building a 'base' or 'parent' controller that gets extended off of by your dynamically called controllers. Those child controllers can have properties that are needed for for the view to render -- honestly I'd need an example to go further. </p> <p>Hopefully this helps a bit. If you ask more specific questions I might be able to give a better thought out opinion.</p>
    singulars
    1. This table or related slice is empty.
    1. POPHP MVC (no framework), should I be calling a lot of methods in my controller or model?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDaniel Doezema
    1. USDaniel Doezema
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPHP MVC (no framework), should I be calling a lot of methods in my controller or model?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COEssentially, controllers gets instantiated by a front controller that turns a/b/c into something like AController, BModel, CAction. I might make MyActionController treat a url like myaction/x/y/z differently, y might be the model, for example. I'm using multiple controllers (that yes, inherit methods and members from an abstract controller class) in order to handle different formats. The main question is when I code these controllers, do I want to be getting the data from the model, storing it and passing it to the view, or returning an object from the model directly to the view render method?
      singulars
      1. PO
      1. USkappasims
    2. COAnd should the model be pretty much a DAL wrapper or should the model be the one that actually "performs" application actions? I see all these axiomatic "PUT APP AND BUSINESS LOGIC IN THE MODEL" statements but I see no real examples. Basically, I want to know if I should go C->M->C->V or C->M->V (where in the first example, data is processed and aggregated from many different model function calls by the controller and passed to the view, or in the second example, the controller just tells the model method to do its thing and the model calls all other model methods that depend on this request)?
      singulars
      1. PO
      1. USkappasims
 

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