Ruby Reports Google Group

Re: Documatic - is this the current repo ?

2009-11-23T22:22:43Z

Hi Thibaut,

Thanks for contacting me. At the moment I'm not doing any development
work in Ruby at all, let alone Documatic.

I certainly agree it would be a good idea to move it to github.com.
Problem is, I can't guarantee I would be able to give it the attention
it deserves (bug fixes, pulling other people's changes etc.). I don't

Re: Documatic - is this the current repo ?

2009-11-23T10:07:03Z

I'm getting in touch with Dave Nelson.

will keep you posted,

Thibaut
--
[link]

Re: [ruport] Re: Documatic - is this the current repo ?

2009-11-17T15:09:53Z

On Tue, Nov 17, 2009 at 3:58 AM, Thibaut Barrère
Thibaut. I definitely won't pull the trigger before ensuring there is
a live copy up somewhere, but not a bad idea.
-greg

Re: Documatic - is this the current repo ?

2009-11-17T08:58:19Z

Hi Greg,

I couldn't find anything matching documatic on github.

Urbanus are you monitoring this list ? What about moving to github ?

If there's no reply, I'll make a copy over at github myself to avoid
this going into the void.

-- Thibaut

Re: [ruport] Documatic - is this the current repo ?

2009-11-16T15:15:36Z

On Mon, Nov 16, 2009 at 5:39 AM, Thibaut Barrère
Actually not sure if urbanus ever got this stuff over to Github. If
not, then yes.
Hopefully he'll move it, because I will eventually take down that old
svn+trac host.
-greg

Documatic - is this the current repo ?

2009-11-16T10:39:49Z

Hello,

just wondering, is this repository the current one for documatic ?

[link]

best,

Thibaut
--
[link]

Re: [ruport] Re: Combining data from two different queries

2009-10-21T01:01:26Z

Hi Andrew. I ended up using a slightly different approach. Instead of
building the table directly from the SQL statement, I created a table
manually using methods on my ActiveRecord objects. It ended up being much
simpler this way. I think I was headed down the wrong path with my question
below.

Re: [ruport] Combining data from two different queries

2009-10-20T23:16:24Z

Hi Karl,
Have you tried using SQL sub-selects? I can never remember the syntax
without looking it up but it's something like:
SELECT signup.code, signup.count, visit.count FROM (SELECT count(*),
c.code FROM signups s......) AS signup JOIN (SELECT ....) AS visit ON
visit.code = signup.code;
You can do this via either model, I don't think it cares what attributes

Combining data from two different queries

2009-10-20T15:21:58Z

On our website we track visits and signups for each of our campaigns. Visit
is a unique visit to the site and a visit is associated with a signup if
that user signs up. I created a table for visits:
s,campaigns c where s.campaign_id=c.id and s.user_id is not null group by code"
+---------------------+

Re: Problem with multiple grouping

2009-10-13T12:16:44Z

Ok, I think I got it.
Having months array I can iterate over months instead of subgroups and
select each subgroup by month. If it exists I can display its
data.size, otherwise just 0.

Re: Problem with multiple grouping

2009-10-13T12:04:03Z

Thanks, this solves the problem with months and I just found out about
the problem you mentioned :)
The code assumes that each user will have entries for every month,
which is not the case, so iterating over sub groups to display the
table doesn't really work that well.

So what's the possible solution?

Re: [ruport] Problem with multiple grouping

2009-10-13T11:41:49Z

Hi Szimek,
Your code assumes that each user will have entries for the same months?
If that's the case, grabbing the keys from the first subgroup hash
should work?
You could also just:
@months = @table.map {|r| r['created_on_month'] }.sort.uniq
If I'm missing something you'll have to explain to me a bit further!

Problem with multiple grouping

2009-10-13T10:47:34Z

Hi,

I'm trying to create a report with user activity across the last few
months. I'd like to create a table where on X axis (table header)
there'd be month names and on Y axis (first table cell in every row)
would be user name.

Here's what I got right now: [link].
The problem is that I don't really know how to diplay all months in

Re: Ruport and WillPaginate

2009-10-05T11:06:20Z

Hello Sylvain,
Thanks for the tips.

Because I need to use :include with ruport, I needed a count method
that works with Ruport but I didn't found one so I created one myself
- using code from report_table from act_as_reportable (see bellow).
def count_table(number = :all, options = {})
only = options.delete(:only)

Re: [ruport] Ruport and WillPaginate

2009-09-23T07:40:22Z

Hi Tygo,
WillPaginate does what you want by default, no need for additional steps.
It has two options you could use :
Instead of loading, counting, then discarding all but the 20 elements
you want, you can do a simple "count" request (ActiveRecord::count or
pure SQL) that will not map DB records to Ruby objects, saving much