Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I don't know all the answers to these but they're interesting questions so I'll have a stab and hopefully someone can fill in the blanks.</p> <p>General</p> <ol> <li><p>Classes not in the default module are prefixed with the module name, e.g. Admin_IndexController and would reside in /admin/controllers. I think the reason for the separation, and inconsistent naming (vs. library classes) is that there would be little benefit having them in a nested folder structure. Controllers are part of your implementation so I think it makes sense, personally. Traversing the folders does get a little tiresome, however.</p></li> <li><p>You could modify the dispatcher, or write a plugin to scan for directories and add them.</p></li> <li><p>There is definitely overlap here - the URL helpers are a good example of this. Generally a view helper generates markup so I think there's a big enough distinction. </p></li> </ol> <p>View</p> <ol> <li><p>I don't know the exact reason but I'd guess it allows other helpers and view functionality to work together more easily. For example, if you've used the doctype helper to set the doctype, the form element helpers can generate XHTML or HTML as appropriate.</p></li> <li><p>It definitely results in a lot of classes, but I'm not sure about maintenance. I've not run in to any problems. I can see the use in static classes, but remember that Zend_View won't stop you using them. If you have your static classes in your include path (and use Zend_Loader or similar), you can use them instead of or in addition to View Helpers.</p></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POZend Framework MVC Design
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDavid Snabel-Caunt
    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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks a lot for some good answers!
      singulars
      1. PO
      1. USrick
    2. COResponse to general question #1: In the name of consistency (which is 1 of 4 traits of good code according to MIT) perhaps controller names should be switched to "Admin_Controllers_Index". It would be more consistent to use a singular "Controller" for the directory and class name.
      singulars
      1. PO
      1. USrick
    3. COResponse to general question #2: Actually, I did write a dispatcher that extended the default standard dispatcher to use a single root directory and have the controllers and directories follow the zf lib naming conventions. In defense of zf flexibility, this was quite pluggable and straight forward.
      singulars
      1. PO
      1. USrick
 

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