Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>I'm putting in params[:year_start]/params[:year_end] for x and y, is that safe to do?</p> </blockquote> <p>You should never embed <code>params[:anything]</code> directly in a query string. Instead use this form:</p> <pre><code>where("date BETWEEN ? AND ?", params[:year_start], params[:year_end]) </code></pre> <blockquote> <p>My actual report probably has closer to 5 database calls and then 6 or 7 calculations on those variables, should I just be querying the date range once and then doing all the work on the array/hash etc?</p> </blockquote> <p>This is a little subjective but I'll give you my opinion. Typically it's easier to scale the application layer than the database layer. Are you currently having performance issues with the database? If so, consider moving the logic to Ruby and adding more resources to your application server. If not, maybe it's too soon to worry about this.</p> <blockquote> <p>I'm really not seeing how I would get the majority of the work/calculations into the model, I understand scopes but how would you put the date range into a scope and still utilise GET params?</p> </blockquote> <p>Have you seen <a href="https://github.com/plataformatec/has_scope" rel="nofollow">has_scope</a>? This is a great gem that lets you define scopes in your models and have them automatically get applied to controller actions. I generally use this for filtering/searching, but it seems like you might have a good use case for it.</p> <blockquote> <p>If you could give an example on creating an array via a broad database call and then doing various calculations on that array and then passing those variables to the template that would be awesome.</p> </blockquote> <p>This is not a great fit for Stack Overflow and it's really not far from what you would be doing in a standard Rails application. I would read the Rails guide and a Ruby book and it won't be too hard to figure out.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat is the 'Rails Way' to implement a dynamic reporting system on data
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USPeter Brown
    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. This table or related slice is empty.
    1. COHi cheers for the answer, don't worry I did mean using ? in the where() so that's at least correct. I feel the main problem is that I need to simplify my question. I really did think this would be much more of a common problem though, maybe I'm using the wrong terminology...
      singulars
      1. PO
      1. USbensmithbwd
    2. CO@bensmithbwd I'd recommend breaking it out into very specific questions. You'll definitely get better responses that way.
      singulars
      1. PO
      1. USPeter Brown
 

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