dynamic table names for AR models

Marnen Laibow-Koser wrote:

Why not create a "wheels" view which combines the data from all the
"wheels_for_*" tables, then tie your Wheel model to that?

Best,
--
Marnen Laibow-Koser
http://www.marnen.org
marnen@marnen.org

I think that would have some performance issues. If there were 20
tables, but only 1 of them contained wheels for the car I was working on
then all 20 tables would have to be checked during a join, no?

Also, that view would not be updatable (updateable?)
Not sure if that is a requirement but something to be aware of.