StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10362209
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-04-28T09:21:50.560
FavoriteCount
0
LastActivityDate
2012-04-28T09:21:50.560
LastEditDate
LastEditorUserId
0
OwnerUserId
1362095
ParentId
10233422
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
i've worked on a few projects that need reporting. the web application stack isn't the best place to do your reporting, but it seems that the open source reporting options are fairly limited. but not every organization can use SSRS or Crystal and in my experience those products are painful and introduce more problems than necessary. I'm using views to get these done. SQL is designed for grouping and aggregating data and it's more equipped to handle this stuff than ruby. however, most of the time, views are going to be executed on the fly, so it's not like you're getting a performance gain here. ideally, after you get a basic implementation, you can set up some cron tasks or means of precalculating the data. and if your reports are going to be accessed often and during the day, you will want a dedicated reporting db. if the reports have to have live data, you will need to set up replication. messing with SQL within Ruby/Rails is messy and frowned upon, I know. So I wrote a gem called Skiima and it helps you manage extraneous SQL objects that you may have in your project. And by loading them with your migrations, it becomes easier to test these. <a href="http://github.com/dcunited001/skiima" rel="nofollow">http://github.com/dcunited001/skiima</a> aside from that, this is what i've been doing: <pre><code>class AccountsReport < ActiveModel attr_accessor :items def initialize(attr = {}) # read in params, set attrs end def execute get_report_items group_report_items summarize_report_groups # if this needs to occur outside of sql end end class AccoutsReportItem < ActiveRecord::Base # you can hook into a view here, you will want the view to return an id col set_table_name :view_accounts_report_items end # yay for arel and activerecord methods. # you can even set up relationships on these. use sparingly. # AccountsReportItem.where(:blah => 'balah') </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGenerating reports efficiently with ActiveRecord
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USdcunited001
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POGenerating reports efficiently with ActiveRecord
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

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.