diff options
| author | Gary Wilson Jr <gary.wilson@gmail.com> | 2008-12-23 00:01:09 +0000 |
|---|---|---|
| committer | Gary Wilson Jr <gary.wilson@gmail.com> | 2008-12-23 00:01:09 +0000 |
| commit | c56535295466e201e330c5d36f04542636f0f6bb (patch) | |
| tree | 4544cd27cc238fef9688a55bb2d517d5b81a1e26 /docs/topics/forms | |
| parent | d66e63f2dc2a5fab29c93e3ca2850a67e30e18f8 (diff) | |
Fixed #9780 -- Fixed an undefined internal link in the model forms documentation, thanks ramiro.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@9670 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/topics/forms')
| -rw-r--r-- | docs/topics/forms/formsets.txt | 2 | ||||
| -rw-r--r-- | docs/topics/forms/modelforms.txt | 12 |
2 files changed, 9 insertions, 5 deletions
diff --git a/docs/topics/forms/formsets.txt b/docs/topics/forms/formsets.txt index 61c2ad377a..c72b0f3c63 100644 --- a/docs/topics/forms/formsets.txt +++ b/docs/topics/forms/formsets.txt @@ -110,6 +110,8 @@ attempt to provide an article, but fail to do so:: As we can see the formset properly performed validation and gave us the expected errors. +.. _understanding-the-managementform: + Understanding the ManagementForm ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt index 0166d4d08a..9a46ffd70c 100644 --- a/docs/topics/forms/modelforms.txt +++ b/docs/topics/forms/modelforms.txt @@ -197,7 +197,8 @@ accepts either ``True`` or ``False``. If you call ``save()`` with the database. In this case, it's up to you to call ``save()`` on the resulting model instance. This is useful if you want to do custom processing on the object before saving it, or if you want to use one of the specialized -:ref:`model saving options <ref-models-force-insert>`. ``commit`` is ``True`` by default. +:ref:`model saving options <ref-models-force-insert>`. ``commit`` is ``True`` +by default. Another side effect of using ``commit=False`` is seen when your model has a many-to-many relation with another model. If your model has a many-to-many @@ -272,7 +273,7 @@ specify ``fields`` or ``exclude`` like this:: class Meta: model = Author fields = ('name', 'title') - + class PartialAuthorForm(ModelForm): class Meta: model = Author @@ -429,7 +430,7 @@ Alternatively, you can create a subclass that implements a ``get_queryset()`` method:: from django.forms.models import BaseModelFormSet - + class BaseAuthorFormSet(BaseModelFormSet): def get_queryset(self): return super(BaseAuthorFormSet, self).get_queryset().filter(name__startswith='O') @@ -496,7 +497,7 @@ number of objects needed:: >>> Author.objects.order_by('name') [<Author: Charles Baudelaire>, <Author: Paul Verlaine>, <Author: Walt Whitman>] - + >>> AuthorFormSet = modelformset_factory(Author, max_num=2, extra=1) >>> formset = AuthorFormSet(queryset=Author.objects.order_by('name')) >>> formset.initial @@ -583,7 +584,8 @@ itself:: </form> When you manually render the forms yourself, be sure to render the management -form as shown above. See the :ref:`management form documentation <understanding-the-managementform>`. +form as shown above. See the :ref:`management form documentation +<understanding-the-managementform>`. Third, you can manually render each field:: |
