On Sun, 2007-05-20 at 11:19 -0700, David Priest wrote:
> I believe I have performed exhaustive research on the challenge of
> creating forms that incorporate fields from multiple tables. I have
> not found *any* comprehensive, best-practices examples of this problem.
>
> It really quite surprises me, as any web application of even moderate
> complexity requires multiple tables.
>
> Anyway, I think everyone (and especially all us n00bs) would *really*
> appreciate a good bit of demonstration code for the following sort of
> scenario:
>
> class Customer(models.Model):
> name = models.CharField()
> phone = models.PhoneNumber()
>
>
> class Rentals(models.Model):
> title = models.CharField()
> serial = models.Integer()
> rented_to = models.ForeignKey(Customer)
> rental_due = models.DateField()
>
> The Form should display the customer's name, phone number, and the
> movies the customer has rented, but *not* the date they're due
> ('cause I'd like this problem to represent real-world problems, where
> one doesn't necessarily display all the fields for editing).
It sounds like you want the django.newforms.formsets capability that
isn't on trunk yet. There is an initial implementation in the
newforms-admin branch because they need it to implement edit-inline
equivalence in the new admin stuff, but it hasn't been completed yet
(based on the FIXMEs at the end of the file), so it isn't worth
committing it to trunk anyway.
A little more patience will be required.
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
