Marnen, in this case, what would you rather use? STI or polymorphism?

On Sep 30, 11:13 pm, Marnen Laibow-Koser <li...@ruby-forum.com> wrote:
> Christian Fazzini wrote:
> > Well its the primary nature of the site. So expect to have tons of
> > media types. Initially, I thought separating them would keep the
> > tables smaller since each media type has its own table.
>
> There's generally no point to keeping tables smaller just for the sake
> of keeping them smaller.  If you have proper indices and well-designed
> queries, your DB should be able to deal with large tables.
>
> STI is perhaps smelly for other reasons (polymorphism or composition is
> often preferable), but in certain cases it really is the best way of
> doing things.
>
>
>
> > Someone mentioned that having it as an STI is fine. Like any other app
> > that becomes huge, we can always optimize?
>
> What's to optimize?
>
> Best,
> --
> Marnen Laibow-Koserhttp://www.marnen.org
> mar...@marnen.org
> --
> Posted viahttp://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-t...@googlegroups.com.
To unsubscribe from this group, send email to 
rubyonrails-talk+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en.

Reply via email to