I've made a quick schema of couple of main tables. As you can see, there are many relations, so I think putting it all in one app. There will be a couple of additional models. There will be 1 more thing: a play systems. Some seasons can have simple table games but others - of example 2 rounds of regular matches etc... That will be a special, separated class for that, in the same app as rest I think.
What do you think? <https://lh5.googleusercontent.com/-qOLlE17nHSg/UcY7Lmq4r5I/AAAAAAAAPQY/Xmb7QGhEqBA/s1600/test.png> On Thursday, June 20, 2013 11:01:30 PM UTC+2, galgal 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.
