In the first place, I have no access to the database design - the django application will be like frontend to already deployed database with loads of information. Furthermore I don't blame the architect for the design, because it's just impossible to store the required information somehow else - it's really complex scientific database. I see some perspective for generalization, but this is out of scope of this problem and project phase :-)
On 14 Spa, 17:39, Javier Guerra Giraldez <jav...@guerrag.com> wrote: > On Thu, Oct 14, 2010 at 4:45 AM, Justinas Jaronis > > <justinas.jaro...@gmail.com> wrote: > > There > > are some objects that will have about 20+ m2m relationships > > not knowing anything about your system, it might be the best solution; > but in the _vast_ majority of cases this is a signal of suboptimal > design. maybe there's some commonality that could be abstracted with > table inheritance, or generic relationships. > > -- > Javier -- 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.
