Tony Drake

@andresgutgon - I already tried re-running CI on this branch. It has something to do with Rails 4.2

The fact model (the Ruby classed inheriting from `ActiveReporting::FactModel` links to a regular active record model. For example, based on you posted, you should have a `Case`, `Diagnosis`, and `Patient`...

The measure is the column stored on the physical database table. So it would go in the database. The Rails model will be able to reference it like any other...

As the way it stands right now, correct. There is one measure column per fact model. This is mainly due to there hasn't been a use case (or someone wanting...

Currently not at this time. I mainly work with relational databases which work well with aggregating data.

The library currently does not. All calculations are done on the SQL level, so something would have to be written to describe how the averages are weighted and translate that...

What would be the output in this "mode" if there's no dimensions defined in the report? I wouldn't be against a PR to see how it would look, though perhaps...

I'm not against this, but I still have issues with naming... So this would introduce a single bool to deviate from the normal output for one usecase. I feel like...

Passing the block does seem awkward... though I can see some utility in it. My concern is we're passing three things into the block and I can see a "need"...