rubyonrailsin

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.

On Mon, Mar 15, 2010 at 10:18 AM, Aldric Giacomoni <lists@ruby-forum.com> wrote:
>
> 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.
> --

--
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.