Thanks colinnkeenan for the suggestion.

Thanks Valentin Lorentz for the report and the suggested fix.

The OmniGraffle source file is included for future use.

Thanks Tim Graham for reporting this issue and testing the fix.

This is a rather large refactoring. The "lookup traversal" code was
splitted out from the setup_joins. There is now names_to_path() method
which does the lookup traveling, the actual work of setup_joins() is
calling names_to_path() and then adding the joins found into the query.

As a side effect it was possible to remove the "process_extra"
functionality used by genric relations. This never worked for left
joins. Now the extra restriction is appended directly to the join
condition instead of the where clause.

To generate the extra condition we need to have the join field
available in the compiler. This has the side-effect that we need more
ugly code in Query.__getstate__ and __setstate__ as Field objects
aren't pickleable.

The join trimming code got a big change - now we trim all direct joins
and never trim reverse joins. This also fixes the problem in #10790
which was join trimming in null filter cases.

The trim argument was used by split_exclude() only to trim the last
join from the given lookup. It is cleaner to just trim the last part
from the lookup in split_exclude() directly so that there is no need
to burden add_filter() with the logic needed for only split_exclude().

The code was dead-code since 2006.

Refs #19368, and the fix introduced in 27f8129d.

Thanks to un33k for the report.

This makes it easier to make a ModelBackend-compliant (with regards to
permissions) User model.

Thanks to cdestigter for the report about the relationship between
ModelBackend and permissions, and to the many users on django-dev that
contributed to the discussion about mixins.

Thanks to gcc for the report.

This documents the behavior introduced by cc337a74, which is BACKWARDS
INCOMPATIBLE for any attempt to invoke a method on a manager using the
abstract class as the calling class (e.g., AbstractBase.objects.do_something())

Thanks to mhsparks for the report.

Thanks Hourann Bosci for the patch.

Fixed #9589 -- Made development web server more robust in the presence of a wider variety of code errors.

Thanks goes to contributor with Trac user 'berto' for the patch.

Thank-you Daniele Procida for the first draft
and shaibi, Aymeric, and others for the reviews.

Removed poor PHP references

Commit was 088d3bc2

If there are more than one values to compare against and the qs isn't
ordered then assertQuerysetEqual will raise a ValueError.

Thanks Kit Sunde for the report and Brian Holdefehr for the initial
patch.

Thanks Chris Jerdonek for the suggestion.

Full disclosure and new release forthcoming.

Some backends might need special handling for auto-increment values.
This was introduced in 5fa5621f. Thanks Michael Manfre for spotting
the issue.

Thanks dloewenherz for the report.

Also fixes #9045.

minor spelling error fix in the docs

Thanks ppetrid for the report.

Thanks joebuyer at manycycles.com for the report and Simon Charette
for the review.