At 2011-12-28 06:59:31 -0800, Jay De Lanoy wrote: > I'd go for a separate table instead, with something like > > class BillingInfo(models.Model): > customer = models.OneToOneField(Customer) > billing_address = models.OneToOneField(Address) > > and then just have logic in the views and templates to account for > existence/nonexistence of a given customer's billing address.
Would this approach mean implementing my own forms to populate customers and addresses and not using the built-in Django admin forms at all? They were a major draw for me to Django. Thanks. --bart -- 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.
