yeah - i'm not sure that there's any elegant way to do it, just a brute force approach of querying every so often and incrementing a count. i think i'll just keep track of the count and not the content of each tweet. all in one db sounds good to me...
- Hide quoted text -
On Sun, Apr 5, 2009 at 4:48 PM, Paul Watson wrote:
> OK, I should be able to get total number of tweets / city / day (on UTC
> time) working within the next couple of days.
Good stuff. I was racking my brain trying to think of a reasonable way
of getting a tweet count for a city. Didn't think of anything.
Are you recording each tweet or just counts?
> Paul, from a db perspective, do you think it makes sense to keep this all in
> one database or have a different database for each city we're tricking
> (where each record would essentially be the total number of tweets for a
> given day)?
I'd keep it all in one database. Rails can but isn't very easy to work
with across multiple databases. Also would make running SickCity.com
with 300+ cities harder.