Well, even if it were possible I wouldn't advise it. The point of the model 
is to model your database, so each table you work with should have a model. 
I would say you'd have two models but have the logic in your method to 
determine which model to interact with.  Hope that helps a bit.

Raul



----- Original Message ----- 
From: "Lucas Campbell" <[EMAIL PROTECTED]>
To: <rubyonrails-deployment@googlegroups.com>
Sent: Monday, February 25, 2008 3:44 PM
Subject: [Rails-deploy] Multiple tables using one model?


>
> Is there a way to use one model to write to different tables if all of
> the tables have the same fields and attributes?
>
> I would like to use one model but be able to decide which table it
> accesses.
>
> Anyone know if this is possible?
> -- 
> Posted via http://www.ruby-forum.com/.
>
> > 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Deploying Rails" group.
To post to this group, send email to rubyonrails-deployment@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-deployment?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to