Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>What I would do is the following.</p> <p>First, create a scope or named_scope in your Project model for finding projects by type. You'll then be able to use this scope to query your projects depending on type.</p> <pre><code># Rails 3 class Project scope :by_type, lambda{ |type| where(type: type.to_i) unless type.nil? } end #Rails 2 class Project named_scope :by_type, lambda do |type| { :conditions =&gt; { :type =&gt; type.to_i } } unless type.nil? end end </code></pre> <p>Next, create a before filter in your controller to load the projects of that type. The before filter should be applied to all pages where you want the buttons to be present:</p> <pre><code>class ProjectsController before_filter :load_projects, :only =&gt; [:index, :action1, :action2] protected def load_projects @projects = Project.by_type(params[:type]) end end </code></pre> <p>Finally, create a partial for the buttons that you can include in the views that have the option of displaying different project types:</p> <pre><code># _project_options.html.erb &lt;%= link_to "Button 1", :controller =&gt; params[:controller], :action =&gt; params[:action], :type =&gt; '1' %&gt; &lt;%= link_to "Button 2", :controller =&gt; params[:controller], :action =&gt; params[:action], :type =&gt; '2' %&gt; &lt;%= link_to "Button 3", :controller =&gt; params[:controller], :action =&gt; params[:action], :type =&gt; '' %&gt; </code></pre> <p>You can then include this partial in each of your related views. And you'll be able to display the projects by doing something like this (if you have an _projects.html.erb partial defined):</p> <pre><code>render @projects </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PORails Beginner - How to define 3 buttons enabling a user to make a choice?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPan Thomakos
    1. USPan Thomakos
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORails Beginner - How to define 3 buttons enabling a user to make a choice?
      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. VTAcceptedByOriginator
    1. COThanks for this, it could be very close to being exactly what we were after.
      singulars
      1. PO
      1. USTexas
    2. COThanks for this, it could be very close to being exactly what we were after. The goal was to have an index page which summarises all the products in the database - before making the changes above, this page was working correctly and was displaying summary information (e.g. Unique brands from the brand column, unique colours, ...). Once the above suggestion was added to the site, this summary information could not be calculated and a nil array was reported. Is this because no button has been pressed yet? If so, is there a way to set a default of assuming Button 3 has been pressed?
      singulars
      1. PO
      1. USTexas
    3. COYes - I modified the controller code in my solution for this case. It basically involves removing the "if params.has_key?(:type)" in the before filter.
      singulars
      1. PO
      1. USPan Thomakos
 

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