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.
I usually avoid doing this, but...
"I want to create a creature with two hands. Is that possible or a bad
idea? I don't want to link them to the same area of the brain because I
want to avoid putting five fingers on each hand".
I mean, maybe I'm completely off, but it sounds like you just want to
create an extra table. What possible benefit could you derive from this,
if the data won't be separate? I guess, if both your tables have 200
fields, you would eventually derive an increase in read speeds if you
don't need all the data.. But I can't think of another reason.
You _can_ do it. Sometimes it's just a really bad idea, but you can
always do it.
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
No comments:
Post a Comment