>> Because I want to save user's info about each game. And the best way
>> is to save the info by each game.
>>
>
> It sounds like you have some db modelling confusion here.
>
> Are you sure you don't just want a many-to-many between Game and User
> with some data on an explicit through model "UserGameInfo" with some
> per-user per-game data?
>
> http://docs.djangoproject.com/en/1.2/topics/db/models/#extra-fields-on-many-to-many-relationships

ok, this is a way.

Let me describe this problem in more detail:
I have a Game model for each game. This model can be seen as a list of
all games, such as,

class Game(models.Model):
    name = models.CharField(max_length = 128, unique = True)
    available = models.BooleanField(default = True)
    timestamp = models.DateTimeField(auto_now_add=True)

And usually a user just plays with a few of games, but there maybe
hundreds of games.
A user may have different level in different games, so I need to keep
record of the user's level in each game.

At the beginning, I want to create a table for each game. Only users
who play that game get their level logged in the game's table.

By using many-to-many field, I can record the level info of all games
in a single table. But I am a little afraid of the performance...

That is the origin of this question. Thank you all. :)

-- 
Best Regards!

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to