Re: [Rails] more than one table per model

Thanks everyone for all your insight. It was very helpful. I was hoping to avoid dereferencing but I guess there's no way around it. I will look into using has_one with a scheduled service for updating the secondary table. Thanks! -- You received this message because you are subscribed to the

Re: [Rails] more than one table per model

On Mon, Mar 15, 2010 at 3:24 PM, Conrad Taylor wrote: > On Mon, Mar 15, 2010 at 10:07 AM, Frank Kim wrote: > >> Hi everyone, >> >> I want to create a model that uses two tables for its data. Is that >> possible or just a bad idea? I don't want to do the has_one because I >> want to avoid the e

Re: [Rails] more than one table per model

On Mon, Mar 15, 2010 at 10:07 AM, Frank Kim wrote: > Hi everyone, > > I want to create a model that uses two tables for its data. Is that > possible or just a bad idea? I don't want to do the has_one because I > want to avoid the extra dereferencing. > > For example > > Model A > - attributes

[Rails] more than one table per model

Hi everyone, I want to create a model that uses two tables for its data. Is that possible or just a bad idea? I don't want to do the has_one because I want to avoid the extra dereferencing. For example Model A - attributes name in first table - attribute phone_num in second table Thanks,