Frank K. wrote:
Okay here’s why I want to do it.
The first table contains just data.
The second table will be a view whose data can change depending on
other external factors. It could change daily.
Yes this second table could be an association but I would have
preferred it not to be.
I don’t think ActiveRecord is going to be your friend here. AFAIK
ActiveRecord expects a model to represent a single database table.
For instance you can override the conventional mapping of a model to a
However, I know of no way to set multiple table names to one model. You
can certainly use more than one model mapped to a single table (STI).
But, not the other way around (again AFAIK).
Beside this, much of the functionality of ActiveRecord would no longer
work. How would it know which tables are represented by the model, and
which attributes belongs to which table. It would not have the benefit
of a join in order to determine what goes where.
Just my 2 cents.