Author: russellm
Date: 2009-09-12 20:35:18 -0500 (Sat, 12 Sep 2009)
New Revision: 11548

Modified:
   django/trunk/docs/topics/forms/modelforms.txt
Log:
Fixed #11740 -- Added extra detail on the behavior of ModelForms. Thanks to 
severian for the suggestion.


Modified: django/trunk/docs/topics/forms/modelforms.txt
===================================================================
--- django/trunk/docs/topics/forms/modelforms.txt       2009-09-13 01:13:40 UTC 
(rev 11547)
+++ django/trunk/docs/topics/forms/modelforms.txt       2009-09-13 01:35:18 UTC 
(rev 11548)
@@ -371,6 +371,35 @@
    ...     class Meta:
    ...         model = Article
 
+.. note::
+
+    If you explicitly instantiate a form field like this, Django assumes that 
you
+    want to completely define its behavior; therefore, default attributes 
(such as 
+    ``max_length`` or ``required``) are not drawn from the corresponding 
model. If 
+    you want to maintain the behavior specified in the model, you must set the
+    relevant arguments explicitly when declaring the form field.
+
+    For example, if the ``Article`` model looks like this::
+
+        class Article(models.Model):
+            headline = models.CharField(max_length=200, null=True, blank=True, 
+                                        help_text="Use puns liberally")
+            content = models.TextField()
+
+    and you want to do some custom validation for ``headline``, while keeping
+    the ``blank`` and ``help_text`` values as specified, you might define 
+    ``ArticleForm`` like this::
+
+        class ArticleForm(ModelForm):
+            headline = MyFormField(max_length=200, required=False, 
+                                   help_text="Use puns liberally")
+
+            class Meta:
+                model = Article
+
+    See the :ref:`form field documentation <ref-forms-fields>` for more 
information
+    on fields and their arguments.
+
 Changing the order of fields
 ----------------------------
 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to