Nick, The UNSIGNED INT data type should be sufficient for ids in the near term. However if you want less maintenance worry in the long run, use UNSIGNED BIGINT as there is a possibility of going over the 4294967295 maximum value of the UNSIGNED INT type at some point for certain ids.
As for length limits: Full name lengths: 20 characters or less Screen names: 15 characters or less Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Sun, Mar 15, 2009 at 2:26 PM, Nick Arnett <nick.arn...@gmail.com> wrote: > > I haven't come across anything in the API docs about what data type would be > appropriate for storing Twitter data in a database. I've heard that Twitter > runs on MySQL, so I'm wondering what the data types are for user and status > IDs. To be on the total safe side, I'm using unsigned BIGINTs, but I'm > wondering if that is wasting space and hurting performance. > Same question for screen_names and real names -- what are their maximum > lengths (I imagine I could figure those out via trial and error, of course)? > TIA, > Nick
