need separate table to store users in db

[tansaku]

So I think twitter-auth is great. However I have run into one issue trying to cache twitter data in the database. I find that I have to have a separate twitter_user table to store user information about friends and followers. If I try and drop it into the users table created by twitter-auth I get validation errors like 'login required'. This means my current db caching of twitter data is a little un-DRY. I wonder if it might be valuable to extract the twitter user data available over the wire to a separate table, and then have the data needed for oauth in a separate table?

[mbleigh]

I think the solution here is to make the validations more optional and flexible instead of requiring a second table for the stored Twitter information. I'll take this under consideration.