I'm currently developing a Social Game (something similar to FarmVill Facebook Game) for Iphone users. Main aim of this game is to allow users to do farming. SO each and every user is capable of farming several types of objects(Apple, Grapes, Banana.. etc).
On my Database I'm holding a separate table to save user information (USER table). This table holds all the user account information.
But to save all of my user's information regarding the game play I maintain a single table (ITEM table). SO in this table I have all the number of farms each user got * number of users. What I mean is...,
The foreign key of this "ITEM" table is set to the "USER" table user id. With this table structure, all the game items belonging to each player is saved on this "ITEM" table. The problem I find in this aspect is that, with number of users increase the entires of this "ITEM" table also increases. Say for instance, 1 user has 50 item objects saved on "ITEM" table. Likewise if there are 100 users, then there will be 50 * 100 = 5000 records in the "ITEM" table.
I want some help on this issue, cuz i thinks this kind of scenario is not a perfect solution on DBMS side.