Rails - Sep 2005 - Few Tables and a lot of reports

Hello !

I am writing a web application. It will have some few tables,
and a lot of ways to query them.

Example: I have the Orders table. The user will be able to select
orders: by customer, by warehouse, by date, by category, etc. etc.
and combinations of them (all customers and warehouse XXX, etc).

TABLES: A, B, C, D, E
REPORTS: R1, R2, R3 ,R4, ..., Rn

Every report should have its own controller, or should be a method
in a Reports controller ?

What is the best design in ROR for an application like this ?

Thank you !


_______________________________________________
Rails mailing list
Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
http://lists.rubyonrails.org/mailman/listinfo/rails

I''d go with one method per report.

-- 
-- Tom Mornini

On Sep 28, 2005, at 4:42 PM, Carlos Pavia wrote:
> Hello !
>
> I am writing a web application.  It will have some few tables,
> and a lot of ways to query them.
>
> Example:  I have the Orders table.  The user will be able  to select
> orders:  by customer, by warehouse, by date, by category, etc. etc.
> and combinations of them (all customers and  warehouse XXX, etc).
>
> TABLES: A, B, C, D, E
> REPORTS:   R1, R2, R3 ,R4, ..., Rn
>
> Every report should have its own controller, or should be a method
> in a Reports controller ?
>
> What is the best design in ROR for an application like this ?
>
> Thank you !
>
>
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>