He means that you can remove: employee = models.ForeignKey(Employee)
from your 'EmployeeAssignment' and 'EmployeeContract' models because the relationship is already defined in your 'Employee' model. You can use reverse relations to get the relation instead. On Aug 8, 10:58 pm, james_027 <[EMAIL PROTECTED]> wrote: > Hi collin > > On Aug 9, 1:06 pm, Collin Grady <[EMAIL PROTECTED]> wrote: > > > Because you have an infinite loop there. > > > Why are you linking both directions? There's a reverse relation > > available to get from EmployeeAssignment and EmployeeContract back to > > the Employee model, you don't need to explicitly define it. > > The EmployeeAssignment and EmployeeContract keeps track the history of > each employee contract and assignment they receive, while the > employee_contract and the employee_assignment attributes tells their > current status ... > > Regards, > james --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---