The only thing that might be a problem is that participants from all kind of events are mixed in one huge table.
When there is a need to do some kind of manual maintenance there is a bigger potential of changing data that belongs to a different event, compared to the old solution where each event had its own isolated tables. Thomas Am Freitag, 11. April 2014 15:57:43 UTC+2 schrieb Gerald Klein: > > it sounds like you are on the right track, only thing is that you may want > to take a look at data normalization in relational databases, this will > give you some clues as to how best link the tables that you are describing > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/d44fe23d-ed2f-459f-badd-52c18cfe9c85%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
