On Fri, 2009-07-31 at 14:42 -0700, Unnamed_Hero wrote: > I have something like this: > > class Translation1(models.Model): > code = models.IntegerField(primary_key=True) > description = models.CharField() > > class Translation2(models.Model): > code = models.IntegerField(primary_key=True) > description = models.CharField() > > class TranslationN(models.Model): > code = models.IntegerField(primary_key=True) > description = models.CharField() > > class MainDB (models.Model): > tr1_code = models.IntegerField() #code from Translation1 > tr2_code = models.IntegerField() #code from Translation2 > tr3_code = models.IntegerField() #code from Translation3
If these are meant to be referring to entries in the tables for Translation1, etc, then make them ForeignKey fields, not IntegerFields. The way you have set up your models, there is no way for Django to know there is any relationship here. [...] > For limiting fields I've created a manager for MainDB, and it works > fine. Then I've tried to do like this: > > > class my_MainDB (MainDB): > tr1_value = models.ForeignKey (Translation1) > > #views.py > result = my_MainDB.gos_req.select_related() #gos_req - my manager > > but I see it is wrong, because djando doesn't know that tr1_value must > be related to tr1_code field... [...] > Is my only way is using this RAW SQL? Unless you are able to fix your modelling, yes. You haven't modelled a system of related data. You have said there are various integers floating around, but not relationships between them. Regards, Malcolm > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
