Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would suggest looking into doing something like the following:</p> <p><strong>Pins.rb</strong>: </p> <p>This will result in having the featured at the top of the list, with a secondary sort of them sorted by when they were created. <em>(Note two methods of sorting by boolean)</em></p> <pre><code>class Pin &lt; ActiveRecord::Base belongs_to :user default_scope order: 'created_at DESC' # Method 1 scope :featy, order('featured DESC, created_at DESC') # Method 2 # scope :featy, order('(case when featured then 1 else 0 end) DESC, created_at DESC') end </code></pre> <p><strong>User.rb</strong>:</p> <pre><code>class User &lt; ActiveRecord::Base has_many :pins end </code></pre> <p><strong>UsersController.rb</strong>:</p> <pre><code>class UsersController &lt; ApplicationController def show @user = User.find(params[:id]) # Pins are accessed via: @user.pins # These should be sorted by `created_at DESC` as that is the default_scope end end </code></pre> <p><strong>users/show.html.erb</strong>: <em>This is all of the users pins sorted by <code>created_at desc</code></em></p> <pre><code>&lt;%= @user.pins %&gt; </code></pre> <p><strong>PinsController.rb</strong>:</p> <pre><code>class UsersController &lt; ApplicationController def index # Pins sorted by created_at: @pins = Pin.all # Pins sorted by created_at with all featured on top: @pins = Pin.featy end end </code></pre> <p><strong>pins/index.html.erb:</strong> <em>This is all pins sorted by <code>created_at desc</code> with all featured on top</em></p> <pre><code>&lt;%= @pins %&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POHaving different database sorting order (default_scope) for two different views
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMichael Lynch
    1. USMichael Lynch
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHaving different database sorting order (default_scope) for two different views
      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
    1. COThis assumes he's calling `.all` AND he's not using Rails 4.
      singulars
      1. PO
      1. USKaleidoscope
    2. COWell all is really just an example i suppose, Its hard to see without more code.
      singulars
      1. PO
      1. USMichael Lynch
    3. COAh, but actually, he can't be using Rails 4 because he's allowed to create scopes that aren't wrapped in `lambda`s. He's probably calling `.all` then, but not necessarily.
      singulars
      1. PO
      1. USKaleidoscope
 

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