Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>After the bootstrap, the only given thing that happens is the menu router system, which figures out which page callback is responsible for this request. To do that, it relies on the information that all the installed modules returned in their <a href="http://api.drupal.org/api/drupal/modules--system--system.api.php/function/hook_menu/7" rel="nofollow">hook_menu()</a> definition (this is stored in the database and only updated when explicitly requested to do so, when new modules are enabled for example).</p> <p>That hook can control <em>a lot</em>. For example access permissions, defining arguments, title of the menu links and so on. Also, menu routers can be almost as complex as you want, they are not limited to the usual controller/action patterns. I think you can define menu router items up to 9 elements deep, for example 'yourmodule/view/%/sub/%/%/whatever'. </p> <p>See <a href="http://drupal.org/node/109131" rel="nofollow">http://drupal.org/node/109131</a> for a short overview with an example.</p> <p>Inside that page callback, the providing module is free to do whatever it wants. It <em>can</em> use the theme system if it wants to, fire hooks or do anything else with the "content" portion of a page. The theme system will include all other portions of a themed page including other regions and other blocks that are included in those regions automatically. This is important to remember when creating callbacks that respond to AJAX request or provide things like xml feeds etc. In those cases you would need to take further steps to make adjustments in the theme to accommodate requests that shouldn't include the "rest" of the page.</p>
    singulars
    1. This table or related slice is empty.
    1. PODrupal's Bootstrap/Dispatch/Routing Flow
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmirzu
    1. USBerdir
    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. VTApproveEditSuggestion
    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. COGot it. So the menu system isn't so much about rending links on the page, but it's actually the router that determines what URLs do what in the system?
      singulars
      1. PO
      1. USAlan Storm
    2. COActually, it's currently pretty much tied to together. Defining menu router items will by default also control the corresponding menu links. So it is kinda responsible for both. This will maybe be decoupled in D8. On top of the menu *system* (includes/menu.inc) is the optional menu.module, which provides (among a few other things) the administrative user interface to create/maintain menus and menu links. But the logic is (mostly) in menu.inc.
      singulars
      1. PO
      1. USBerdir
    3. COThis linkage is the cause of many tears. Many tears.
      singulars
      1. PO
      1. USmirzu
 

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