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 how much more help I can be, but I understand your pain having just come to rails myself. The article recommended by ghoppe, "Skinny Controller, Fat Model" explains the function of Ms Vs &amp; Cs nicely. Seeing as that does not fully answer your question I will try to explain the mechanics of each structure.</p> <h2>Model</h2> <pre><code>class Account &lt; ActiveRecord::Base belongs_to :user validates_presence_of :address def name # Account does not have a name field, but User does so I will make a name method for Account and feed it name of the user it belongs to. user = self.user # Account gets the user method with the &lt;belongs_to :user&gt; association # note: Rails expects Accounts to have a user_id field so it can perform the "magic" to associate Accounts with Users if user.name return user.name else return nil end end end </code></pre> <p>The model describes your object. Like an object in any OOP language you want to put all of your object logic here. This includes the rails helpers for association(has_one, belongs_to, ...) and validation, as well as any other method or library you want the object to be able use throughout your Models Views and Controllers. </p> <h2>Controller</h2> <pre><code>class AccountsController &lt; ApplicationController before_filter :name, :only =&gt; :edit, :destroy # @account.name will be executed before the edit or destroy method(action) can be invoked on @account. If the user who has the account has a name the action will execute. def index # This is a RESTful action and is mapped by Rails by default to an HTTP GET request. Rails expects an index.html.erb or index.haml.erb or index.something in the Accounts view to map this action to. @accounts = Account.all # @accounts is an instance variable and will be accessible in the view this action is mapped to. end def show @account = Account.find(params[:id]) # params[:id] is passed to the controller from the view. The params hash is the primary tool form moving data from a form or URL into a controller. Anytime you click on the link_to the show or edit action of an object Rails will put that objects id in the params hash and call the appropriate action in that objects controller. If you click the show link on an account it will call this action. Now the instance variable in the view show.html.erb will hold a single account instead of an array end def new @account = Account.new # This initializes a new account with all the fields set to blank unless you specified a default in your migration. This account has not been save to the db yet. It is ready for a user to fill in. respond_to do |format| # Rails can automatically respond differently to different client request. If a client i.e browser wants HTML rails responds with HTML. If a client e.g. an API want XML Rails responds with XML. format.html # new.html.erb # format.xml { render :xml =&gt; @account } end end def edit @account = Account.find(params[:id]) # Same as show, but mapped to a different view end def create # Finally we have a POST. All the prior actions were GETs, but now we are saving some data to the db. @account = Account.new(params[:account]) # The :account key is special. It is a hash of hashes. It is populated by the form fields in new.html.erb. To access a specific field such as address we say &lt;params[:account][:address]&gt; and whatever the user entered in the address field in the View is at out fingers in the Controller. respond_to do |format| if @account.save # If the validations pass and the account gets saved redirect to the show page of the new record, otherwise refresh/render the new page (hopefully showing what error caused the record to fail to save). format.html { redirect_to(@account, :notice =&gt; 'Account was successfully created.') } format.xml { render :xml =&gt; @account, :status =&gt; :created, :location =&gt; @account } else format.html { render :action =&gt; "new" } format.xml { render :xml =&gt; @account.errors, :status =&gt; :unprocessable_entity } end end end def update # This is another of the seven RESTful Rails actions and results in a PUT request because you are updating an existing record @account = Account.find(params[:id]) respond_to do |format| if @account.update_attributes(params[:account]) format.js # Rails can also respond with JavaScript. Look up UJS. Rails 3 has made large improvements here. format.html { redirect_to(@account, :notice =&gt; 'Account was successfully updated.') } format.xml { head :ok } else format.js format.html { render :action =&gt; "edit" } format.xml { render :xml =&gt; @account.errors, :status =&gt; :unprocessable_entity } end end end def destroy # This results in a DELETE @account = Account.find(params[:id]) @account.destroy # destroy is a more thourough delete and will check the options of this records associations and destroy the associated objects as well if they are dependant on this object. The option &lt;:dependant =&gt; :destroy&gt; is not set for this object's only association: User. The user this account belongs to will therefore survive the destruction of this account. respond_to do |format| format.html { redirect_to(accounts_url) } format.xml { head :ok } end end end </code></pre> <h2>View</h2> <p>Hopefully you can draw your own logic from here. The view is designed to render information passed as instance vars from a controller to a client: browser, api, smart phone. As well as to pass information from a client to the controller via the params hash. No complicated logic should get performed in a view even though a view with erb has the capability to execute any ruby code.</p> <p>If an example view would also be helpful I am happy to oblige. </p>
    singulars
    1. This table or related slice is empty.
    1. POGive a detailed illustration of how the MVC works in Rails, and how the controller communicates with forms etc?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USsmothers
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POGive a detailed illustration of how the MVC works in Rails, and how the controller communicates with forms 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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWow DUDE. I must say....this has to be the most comprehensive, and well-thought through response I have ever gotten on any question I have asked. Thanks so much for taking the time man. Really appreciate it.
      singulars
      1. PO
      1. USmarcamillion
    2. COGlad it helped. I had the same question not three months ago. Takes one to know one eh.
      singulars
      1. PO
      1. USsmothers
    3. COSO how did you conquer it so quickly? You coming from a Ruby background? Or a heavy programming background? I have been trying to slay this beast for a few months too...and even though I am making progress, it is tough, slow...step by step progress. Sometimes I feel like I hit a mountain and it is painful to get to the other side. How did you get over these problems, if you experienced any of them?
      singulars
      1. PO
      1. USmarcamillion
 

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