| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
reverse side of a related set.
|
|
|
|
|
|
|
|
| |
modelformset instances
Too much field exclusions in form's construct_instance() in _post_clean()
could lead to some unexpected missing ForeignKey values.
Fixes a regression from 45e049937. Refs #13776.
|
| |
|
|
|
|
| |
on_delete for ForeignKey/OneToOneField
|
|
|
|
| |
with auto-PK children.
|
|
|
|
| |
updated related instance.
|
|
|
|
| |
key's that have defaults.
|
|
|
|
|
|
| |
field classes.
Thanks Carl Meyer and Markus Holtermann for the reviews.
|
| |
|
| |
|
|
|
|
| |
Django test suite.
|
|
|
|
| |
error message.
|
| |
|
|
|
|
|
|
| |
combining FormSet.min_num and FormSet.extra.
Forwardport of 79f15ab1ef from stable/1.7.x
|
|
|
|
|
|
|
|
| |
inlines, and the admin.
Thanks Stephen Burrows for work on the patch as well.
Forwardport of 2914f66983a92fcae55673c517dd8d01e8c238c4 from stable/1.7.x
|
|
|
|
|
| |
Oracle and SQL Server don't have exactly the same limitations. It's
worth treating them differently.
|
|
|
|
|
|
| |
docs and tests.
Thanks tomwys for the suggestion.
|
|
|
|
|
|
|
|
| |
of fields is not specified.
Also applies to modelform(set)_factory and generic model views.
refs #19733.
|
| |
|
|
|
|
| |
Signed-off-by: Jason Myers <jason@jasonamyers.com>
|
| |
|
|
|
|
|
|
| |
ModelFormSet
The ticket's issue was already fixed by patch for #14877.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
BooleanField does not have a default value
Thanks to Collin Anderson for the suggestion and Tim Graham for
reviewing the patch.
|
|
|
|
|
| |
Should be unneeded with Python 2.7 and up.
Added some unicode_literals along the way.
|
| |
|
|
|
|
|
|
| |
longer deletes objects
Thanks laureline.guerin@ and Wedg.
|
|
|
|
|
|
|
|
| |
exponential notation.
Browsers parse small factors of 10 as 0 under decimal notation.
Thanks to Trac alias matklad for the report and Claude Paroz for the review.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
BaseModelFormSet init
BaseModelFormSet.forms is now a cached property instead of being
populated in the __init__ method. This behaviour also matches an
example in the documentation.
Thanks Thomasz Swiderski for the report and Simon Charette for the
review.
|
|
|
|
|
|
|
|
|
| |
`NumberInput`.
This attribute is only allowed on inputs of type "text", "search", "url",
"tel", "email", or "password".
Thanks to yoyoma for the report and @bmispelon for the review.
|
|
|
|
| |
label, help_text and error_messages
|
|
|
|
|
|
|
|
| |
'exclude', and added '__all__' shortcut
This also updates all dependent functionality, including modelform_factory
and modelformset_factory, and the generic views `ModelFormMixin`,
`CreateView` and `UpdateView` which gain a new `fields` attribute.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
max_num on server.
This is provided as a new "validate_max" formset_factory option defaulting to
False, since the non-validating behavior of max_num is longstanding, and there
is certainly code relying on it. (In fact, even the Django admin relies on it
for the case where there are more existing inlines than the given max_num). It
may be that at some point we want to deprecate validate_max=False and
eventually remove the option, but this commit takes no steps in that direction.
This also fixes the DoS-prevention absolute_max enforcement so that it causes a
form validation error rather than an IndexError, and ensures that absolute_max
is always 1000 more than max_num, to prevent surprising changes in behavior
with max_num close to absolute_max.
Lastly, this commit fixes the previous inconsistency between a regular formset
and a model formset in the precedence of max_num and initial data. Previously
in a regular formset, if the provided initial data was longer than max_num, it
was truncated; in a model formset, all initial forms would be displayed
regardless of max_num. Now regular formsets are the same as model formsets; all
initial forms are displayed, even if more than max_num. (But if validate_max is
True, submitting these forms will result in a "too many forms" validation
error!) This combination of behaviors was chosen to keep the max_num validation
simple and consistent, and avoid silent data loss due to truncation of initial
data.
Thanks to Preston for discussion of the design choices.
|
|
|
|
| |
ModelMultipleChoiceField
|
|
|