| Age | Commit message (Collapse) | Author |
|
Conflicts:
django/db/backends/mysql/introspection.py
django/db/backends/oracle/creation.py
django/db/backends/postgresql_psycopg2/creation.py
django/db/models/base.py
django/db/models/loading.py
|
|
specify app_label.
Thanks mark@ and Aramgutang for work on the patch.
|
|
|
|
Thanks Jeff250.
|
|
Thanks tunixman for the suggestion and Loic Bistuer for the review.
|
|
Thanks jonash.
|
|
Thanks Patryk Zawadzki.
|
|
|
|
|
|
|
|
|
|
In the intervening years, RelatedField has become less of a hack (though it still is one). Anyone who wants to can re-instate the comment, but please add more details.
|
|
|
|
Thanks stanislas.guerra at gmail.com for the report and
Baptiste Mispelon for the review.
|
|
|
|
|
|
Conflicts:
django/db/backends/__init__.py
django/db/models/fields/related.py
tests/field_deconstruction/tests.py
|
|
This is to help other ongoing branches which would benefit from
this functionality.
|
|
Add support for Oracle, fix an issue with the repr of RawQuerySet,
add tests and documentations. Also added a 'supports_paramstyle_pyformat'
database feature, True by default, False for SQLite.
Thanks Donald Stufft for review of documentation.
|
|
|
|
Those methods were only used by `contrib.admin` internally and exclusively
related to `contrib.auth`. Since they were undocumented but used
in the wild the raised deprecation warning point to an also undocumented
alternative that lives in `contrib.auth`.
Also did some PEP8 and other cleanups in the affected modules.
|
|
|
|
Conflicts:
django/db/models/loading.py
|
|
Thanks lsaffre for the report and simon29, vicould, and Florian Hahn
for the patch.
Some changes done by committer.
|
|
fields
|
|
as the exception bubbles up
|
|
There were a couple of places which used Query.join() directly. By
using setup_joins() in these places the code is more DRY, and in
addition there is no need to directly call field.get_joining_columns()
unless the field is the given join_field from get_path_info(). This
makes it easier to make sure a ForeignObject subclass generates joins
correctly in all cases.
|
|
|
|
The join used by select_related was incorrectly INNER when the query
had an ORed filter for nullable join that was trimmed away. Fixed this
by forcing the join type to LOUTER even when a join was trimmed away
in ORed queries.
|
|
Thanks carbonXT for the report.
|
|
This can be used to make Django's test suite significantly faster by
reducing the number of models for which content types and permissions
must be created and tables must be flushed in each non-transactional
test.
It's documented for Django contributors and committers but it's branded
as a private API to preserve our freedom to change it in the future.
Most of the credit goes to Anssi. He got the idea and did the research.
Fixed #20483.
|
|
|
|
Conflicts:
django/db/models/fields/related.py
|
|
The patch for #19385 caused a regression in certain generic relations
.exclude() filters if a subquery was needed. The fix contains a
refactoring to how Query.split_exclude() and Query.trim_start()
interact.
Thanks to Trac alias nferrari for the report.
|
|
This method is useful to discover files inside apps.
|
|
|
|
Thanks Carl for the suggestion and David Cramer for the patch.
|
|
Thanks Gavin Wahl.
|
|
Correctly calculate the ``aggregate_start`` offset from loaded fields,
if any are deferred, instead of ``self.query.select`` which includes all
fields on the model.
Also made some PEP 8 fixes.
|
|
Thanks wilfred@, poirier, and charettes for work
on the patch.
|
|
Thanks simon@ for the suggestion and JordanPowell
for the initial patch.
|
|
The SubqueryConstraint defined relabeled_clone(), but that was never
called. Instead there is now clone() and relabel_aliases() methods for
SubqueryConstraint.
A related problem was that SubqueryConstraint didn't correctly use
quote_name_unless_alias() of the outer query. This resulted in failures
when running under PostgreSQL.
|
|
|
|
|
|
Thanks to av@rdf.ru and flarno11@yahoo.de for the report.
|
|
|
|
When an exception other than IntegrityError was raised, get_or_create
could fail and leave the database connection in an unusable state.
Thanks UloPe for the report.
|
|
|
|
|
|
fields.
This is backward incompatible for custom form field/widgets that rely
on the hard-coded 'Hold down "Control", or "Command" on a Mac, to select
more than one.' sentence.
Application that use standard model form fields and widgets aren't
affected but need to start handling these help texts by themselves
before Django 1.8.
For more details, see the related release notes and deprecation timeline
sections added with this commit.
|