AlwaysCharging wrote: [...] > > On Oct 19, 9:22�am, Marnen Laibow-Koser <rails-mailing-l...@andreas- > s.net> wrote: >> AlwaysCharging wrote: >> > I was reading this article a while back >> >http://www.sitepoint.com/blogs/2008/06/06/did-rails-sink-twitter/ >> > and it got me thinking. �If I wanted to set up my app so that each >> > user has his/her own table, how would I go about doing that? >> >> You wouldn't. �It's a horrible idea, and whoever wrote the article >> doesn't appear to understand good database design. �There are other ways >> to achieve good performance. > > Umm... and examples of that would be ... ?
Decently normalized tables, proper use of indices, perhaps some DB performance tuning. Basically, remember that DB servers were *designed* for problems of this type, without kludgy solutions such as we're discussing. And Rimantas is right, you seem to be trying to prematurely optimize. Learn about the standard methods of database design before you try weird things like this. Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
