On 29/12/2012 7:39pm, Taras_96 wrote:
f we map software objects directly onto Django Models, then we'd end up with a TimeWindow table, where each row would only ever be referenced by exactly one Event. My understanding of the advantage of normalisation is that it prevents data duplication, and thus helps with data consistency. However, it doesn't really make much sense to incur the cost of this (through joins) if the object that is being modelled is a value object.
If there is a genuine one-to-one relationship you can be a bit relaxed about making it part of the event table. That won't duplicate anything.
But there is nothing wrong with being rigorously 3rd normal form right now and then optimising later - if necessary.
Mike -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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.
