A common practice for Twitter application developers is creating a MySQL table to store user objects returned from Twitter’s API. I’m trying to optimize my user table for Friend Or Follow, and it occurred to me how many developers must be reinventing this MySQL table schema, so let’s get it right once and for all.
Here’s where I’m starting. If you see anything that I’m missing, or notice a data type that could be optimized let me know in the comments and I’ll update the post to reflect your suggestions.
3 thoughts on “Twitter MySQL User Object Table Schema”
hi. can you please provide a python script to insert the twitters GetFriendsTimeline into mysql??
when i tried doing it, i got a ‘UnicodeEncodeError: ‘latin-1′ codec can’t encode character u’\u2013’ in position 16: ordinal not in range(256)
‘ error in python.
Hey beautiful – I love friendorfollow and have used it for ages on a couple of Twitter accounts. But I am getting this error message when I try to use FoF with my new Twitter account. What can I do? xx
” wz_tooltip.js must be included INSIDE the body section, immediately after the opening tag.”
I wish I had seen this before I built my site. 😛
Hi Dusty. I was sitting behind you at one of the presentations at Twitter. We didn’t get to talk, but I wish you continued success with Friend or Follow.