Hi Taliesin, Here is what I would do; I would set up relationships like this Contact -> Division -> Account. Then you can access a contacts account as `contact_instance.division.account`. This means you need to create a Division for each Account that represents no-division. It can be done automatically within Account.save() or via signals. I am aware this introduces some comlexity and queries spanning over three tables should run slower than queries spanning over two tables, but I believe this is simple and not horribly inefficient.
Regarding limiting ForeignKey choices question; take a look at `limit_choices_to`. Well documented as usual. For composite FK question; AFAIK Django doesn't support them. If you can't find an answer here I suggest you to try StackOverflow as well. Regards, -- Saygılarımla, Atamert Ölçgen -+- --+ +++ www.muhuk.com mu...@jabber.org -- 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.
