On 11/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > the models file has a slew of fields in it (for the columns in the > database). Just wondering if the other fields can't be null.
Correct (unless your model defines the fields as blank=True, null=True, which makes them completely optional at the database level). If you want a restricted version of the form that only displays one field, you will need to create a custom manipulator. > Also, > wondering if there's a trick to map the form names to the view to be > saved. I'm unclear what you are asking for - the field names on the form are tied to the attribute names of the object being saved - what does the view have to do with it? Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
