I\'m trying to determine the best table design for a \"follow/unfollow user\" feature, similar to Twitter (edit: I\'m not making a Twitter-like application.
I would suggest you make follower and following together the primary key. There is no need for a seperate id
field.
I think it's a very good design, and should meet your needs nicely. One thing; you should probably make the follower
and following
foreign keys. Oh, and for simplicity sake, I'd make the subscribed
column TIMESTAMP DEFAULT CURRENT_TIMESTAMP
just to capture the datetime the user subscribed.