Just some generic advice -- keep each app focused on one individual task,as a rule of thumb you'd want maybe 5 +/- 2 models per app. Better to have multiple apps that each do one thing well than one large app that does everything.
Best On Thu, Jun 20, 2013 at 5:01 PM, galgal <weglarek.rob...@gmail.com> wrote: > Hi, > I'm starting my new project. It's sport-connected. > The main part of my app will be league, matches, teams and players. There > will be many relations. > > So, how to make apps and models. I plan to make models: > > - Season > - League (FK to Season) > - Team > - Match (FK to League and 2FK to Teams) > - Players (FK to Team) > - and many more to present teams history in each season etc. > > Is it better, to make it all in 1 app, called for example Game, or divide > it into smaller apps? > Thanks for help. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Mayukh Mukherjee http://www.linkedin.com/in/mayukhmmukherjee -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
