No, the foreign key looks the same, but logically it's for different purpose. You can easily imagine a table of Paint Suppliers, with a field for their cheapest color product. And another table listing all color products from all suppliers, with a field identifying which supplier owns the product. Thus, both table has foreign keys crisscrossing each other.

oggie rob wrote:

So what do you need the extra table for?! Can't you just use:
class Company(meta.Model):
  ...
class Acount(meta.Model):
    company = meta.ForeignKey(Company)

and then things like:
account.get_company()
company.get_accounting_account_list()

 -rob



Reply via email to