| Age | Commit message (Collapse) | Author |
|---|
|
I refactored RadioSelect and CheckboxSelectMultiple to
make them inherit from a base class, allowing them to share
the behavior of being able to iterate over their subwidgets.
Thanks to Matt McClanahan for the initial patch and to
Claude Paroz for the review.
|
|
|
|
|
|
Thanks burton449geo at gmail.com for the report.
|
|
|
|
|
|
|
|
The phrase "if it exists" was used in reference to the `decimal_places`
argument to `DecimalField`, when in fact that field is required.
|
|
This trailing space may seem innocuous, but can be easily copied-and-pasted from the docs.
This can lead to bizarre File Not Found errors where the checked paths look correct, but actually aren't because
the trailing space is hard to see in an error message.
|
|
|
|
|
|
|
|
Thanks rshea for the draft text.
|
|
|
|
the need for updating the system's map files when incorrect content types are returned. Many thanks to Simon Charette and Claude Paroz for their feedback.
|
|
|
|
Thanks Jan Murre, Reinout van Rees and Wim Feijen,
plus Remco Wendt for reviewing.
|
|
Ref #19689.
|
|
Thanks Stefan Berder.
|
|
Removed ambiguity regarding LANGUAGES setting
|
|
|
|
The docs to the LANGUAGES setting were using both the term language code
and language name for the same thing.
|
|
Fixed signature of HttpResponse.set_signed_cookie in docs.
|
|
|
|
|
|
Thanks to the many contributors who updated and improved the patch over
the life of this ticket.
|
|
Fixed #18000 -- Moved the code to handle goto requests to an extra WizardView method.
|
|
|
|
without the need to add them in the as_view call.
|
|
|
|
|
|
change_list_request.html doesn't exist, it's named change_list_results.html
|
|
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.
|
|
Thanks martinogden for the initial patch and d1ffuz0r for tests.
|
|
|
|
MySQL accepts 0000-00-00 as a valid date but MySQLdb converts those
values into None. So there will be problems for instance if trying to
transport the data using dumpdata/loaddata.
This patch refs #6642 that has been closed as wontfix since this is a
particular problem of MySQL.
|
|
|
|
|
|
|
|
|
|
When the 'invalid' error message is set at field level, it masks
the error message raised by the validator, if any.
|
|
Model.save() will use UPDATE - if not updated - INSERT instead of
SELECT - if found UPDATE else INSERT. This should save a query when
updating, but will cost a little when inserting model with PK set.
Also fixed #17341 -- made sure .save() commits transactions only after
the whole model has been saved. This wasn't the case in model
inheritance situations.
The save_base implementation was refactored into multiple methods.
A typical chain for inherited save is:
save_base()
_save_parents(self)
for each parent:
_save_parents(parent)
_save_table(parent)
_save_table(self)
|
|
|
|
|
|
Replaced them with per-database options, for proper multi-db support.
Also toned down the recommendation to tie transactions to HTTP requests.
Thanks Jeremy for sharing his experience.
|
|
Technically speaking they aren't usable yet.
|
|
This is mostly a documentation change.
It has the same backwards-incompatibility consequences as those
described for PostgreSQL in a previous commit.
|
|
Fixed #20018
|
|
By default, show tracebacks for management command errors when the
exception is not a CommandError.
Thanks Jacob Radford for the report.
|
|
return a QuerySet.
|
