On Oct 19, 10:38 am, AlwaysCharging <goodg...@gmail.com> wrote:
> Thank you for the reply.
>
> I would, but that's exactly what that article was saying to steer
> clear of, and it makes sense. If you have to keep querying the same
> table for everyone's new posts and post them back to your "feed" of
> the people that you follow, wouldn't that cause serious bottlenecks
> and lead to outages? (which is exactly what I think is/was happening
> with twitter)
>
I think you misread the article - I don't think it is suggesting one
table per user.
it's saying
select * from tweet_queue where tweet_queue.user_id = 123456 AND ...
rather than
select * from tweets
inner join followings on followings.followee = tweets.user_id
where followings.follower_id = 12456 AND ...
Fred
> And right now I'm just at the hypothetical stage as I'm still learning
> rails, so I don't have any constraints or requirements of what I'm
> trying to do. I was just saying if my app was heavily intensive on
> user read/writes so that other users could follow other users,
> wouldn't it be best to give each their own table?
>
> On Oct 19, 4:53 am, Colin Law <clan...@googlemail.com> wrote:
>
>
>
> > 2009/10/19 AlwaysCharging <goodg...@gmail.com>:
>
> > > 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?
>
> > > "create_table :users" just creates a table in the database for a list
> > > of all the users (which I guess I'd want in addition to their
> > > individual tables), but is there a way to make it create an new table
> > > for each user? Would this even be the best way if my app allowed
> > > "followers?" Admittedly there'd be a ton of tables in my database,
> > > but wouldn't it make it easier for indexing all of your followers
> > > messages?
>
> > > Any insight is greatly appreciated.
>
> > Why not just put the information in the users table? If you think
> > this is not an appropriate solution give more details of the
> > requirement so we can see what you are trying to do.
>
> > Colin
--~--~---------~--~----~------------~-------~--~----~
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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
