Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In a very small nutshell:</p> <p><strong>Block</strong> are responsible for rendering content (everything from frontend, backend, emails, and more). If content is being displayed somewhere chances are it is a block.</p> <p><strong>controllers</strong> are responsible for processing all requests made via a url. If you hit the url <a href="http://www.example.com/catalog/product/view/id/9/">http://www.example.com/catalog/product/view/id/9/</a> you hit the <em>catalog</em> module in the <em>controllers/ProductController.php</em> and inside of that the <em>viewAction()</em> method. If you hit a URL in Magento the request passes through one or more controllers.</p> <p><strong>etc</strong> contains any configuration xml files for the modules. These are responsible for everything from ACL (access control lists) to how to access blocks/models etc to system configuration settings. Some sample files:</p> <ul> <li>adminhtml.xml - Handles much of the admin side. It handles ACL and Menu control. This file is optional.</li> <li>config.xml - Handles all the base configurations for a module. This file defines how/where to find helpers, blocks, models, resources, default module settings, rewrites, observers, frontend layout files, and a slew of other configurations. This file is required for a module to function.</li> <li>System.xml - Contains all system configurations inserted into the System -> Configuration section of the site.</li> <li>There are others, but they are more advanced topics than what you are asking for.</li> </ul> <p><strong>Helper</strong> - These files are "helpers". They contain functions that are common to the module or that may be accessed by other modules. One functionality of these is to provide translations. In addition, Data.php is the default helper that is included here. If you have system configurations a Data.php is required for the system configuration to appear correctly.</p> <p><strong>Model</strong> - These are your objects of data. For example a Product or Category is a model. They provide data management functions. They interface with a Resource folder contained in the model folder to access the database, and Collections to get a collection of objects.</p> <p><strong>sql</strong> - These are your setup scripts. When a module is installed if configured correctly some changes might need to be made to the database: adding tables, attributes to products, or custom configurations.</p> <hr> <p>I recommend taking a look at <a href="http://alanstorm.com/category/magento">http://alanstorm.com/category/magento</a></p> <p>He has many samples, tutorials, and other good tips and is a more complete starting place.</p>
    singulars
    1. This table or related slice is empty.
    1. POMagento Model vs Block vs Controller etc
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USIan
    1. USIan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMagento Model vs Block vs Controller etc
      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. COWhy are Blocks, Helper, and Model capitalized, but not the others? Also, why are Block and controllers pluralized, but not the others? That seems like a very confusing way of doing things.
      singulars
      1. PO
      1. USswl1020
    2. COI made a typo, Blocks was supposed to be Block. "controllers" should be the only plural. There is no functional reason that I know of for plural vs singular, it was a design decision by the Magento development team. Block/Helper/Model are capitalized to signify they are objects that can be instantiated by you in code. You can instantiate a Block, Helper, and Model but you cannot instantiate anything inside of etc, controllers, or sql. Not to say you can't access a configuration setting inside config.xml but you can't instantiate it.
      singulars
      1. PO
      1. USIan
    3. CO@Ian, there is a [Magento SE site proposal](http://area51.stackexchange.com/proposals/48872/magento?referrer=OO7r6fZfer327y6ehRWkiw2) which is very near reaching beta phase. The purpose of the proposal is to have a dedicated Q&A site for Magento allowing us to better server the community. We currently need a few (seriously, only seven) more individuals to commit to the proposed site to reach beta. [Check it out](http://area51.stackexchange.com/proposals/48872/magento?referrer=OO7r6fZfer327y6ehRWkiw2) and lend your support if you can! :)
      singulars
      1. PO
      1. USdavidalger
 

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