Andreas S. wrote: > Ichiro Saga wrote: >> That's why I was thinking about breaking it into some >> smaller tables. > > Don't. A few 100k or million rows are nothing for a database. As long as > you set up an index for the school_id, splitting the students in > multiple tables has absolutely no advantage.
Right. If you *must* break the table (which you probably won't even need to do), then use your DB's sharding features (such as MySQL's MERGE tables) so that it still functions like one huge table. Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org -- 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-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.
