Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think you're somewhat on the right track with the latter approach. However, you should not hard code the calling of actions in your bootstrap. The bootstrap should interpret the URL and call the action methods dynamically through the use of a function like <code>call_user_func_array</code>.</p> <p>Also, I would suggest that you leave the rendering of views up to the action code so the action logic is self sufficient and flexible. That would allow the action to analyse the input for correctness and render errors or views appropriately. Also, you've got the method 'deleteItem' on your controller, but that should really be the work of a model. Perhaps you should read up some more on MVC and try to work with an existing framework to understand the concepts better before you try to implement your own framework (I would suggest the Yii framework for that).</p> <p>Here's an example of how <strong>I think</strong> your logic should be implemented in a good MVC framework.</p> <pre><code>class ListController extends BaseController { public function CreateAction($title){ if(ctype_alnum($title)) { $list = new List(); $list-&gt;Title = $title; if($list-&gt;insert()) { $this-&gt;render_view('list/create_successful'); } else { $this-&gt;render_view('list/create_failed'); } } else { $this-&gt;render_view('list/invalid_title'); } } public function DeleteAction($id){ $list = List::model()-&gt;getById($id); if($list == null) { $this-&gt;render_view('list/errors/list_not_found'); } elseif($list-&gt;delete()) { $this-&gt;render_view('list/delete_successful'); } else { $this-&gt;render_view('list/delete_failed'); } } } </code></pre> <p><a href="http://anantgarg.com/2009/03/13/write-your-own-php-mvc-framework-part-1/" rel="nofollow">here is a great tutorial on how to write your own MVC framework</a></p>
    singulars
    1. This table or related slice is empty.
    1. POPHP MVC design - multiple actions to same url/controller
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSaad Imran.
    1. USSaad Imran.
    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. VTDownMod
    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. COThanks for this. To make it clear,in the above the controller->deleteItem method would merely call a DAO object which would handle the delete. I wasn't explicitly calling the database functions in the controller. I was just a bit confused about where multiple requests to the same page sit, but I guess it's more about how I handle the "actions" and where I build those up in my urls
      singulars
      1. PO
      1. USTommyBs
    2. COOh okay, I understand. In any case, I think your bootstrap should analyse only the URL request when it decides which controller and action to execute, the POST data should play no part in it (in my opinion). Like you said, it's more about how you choose to build your actions, I think it would make more sense to have `Delete` and `Create` actions rather than a `Post` action, because they really are two different actions. You should try looking into the `CRUD` pattern, it goes nicely with MVC and might give you new ideas.
      singulars
      1. PO
      1. USSaad Imran.
 

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