summaryrefslogtreecommitdiff
path: root/django/db
AgeCommit message (Collapse)Author
2015-09-26Fixed #25421 -- Fixed test --keepdb option on Oracle.Mariusz Felisiak
2015-09-25Fixed #25196 -- Normalized database representations in test database messages.Ville Skyttä
Left over Oracle mostly as-is since it's more complicated.
2015-09-24Removed unused Aggregate.input_field.Tim Graham
Obsolete since 4a66a69239c493c05b322815b18c605cd4c96e7c.
2015-09-24Refs #14030 -- Removed more backwards compatiblity for old-style aggregates.Tim Graham
Per deprecation timeline.
2015-09-23Refs #21414 -- Removed Field.related per deprecation timeline.Tim Graham
2015-09-23Refs #14030 -- Removed backwards compatiblity for old-style aggregates.Tim Graham
Per deprecation timeline.
2015-09-23Refs #9893 -- Removed shims for lack of max_length support in file storage ↵Tim Graham
per deprecation timeline.
2015-09-23Removed SQLCompiler.__call__() per deprecation timeline.Tim Graham
2015-09-23Refs #12663 -- Removed deprecated Model._meta methods.Tim Graham
2015-09-23Removed SubfieldBase per deprecation timeline.Tim Graham
2015-09-23Refs #24351 -- Removed support for the old allow_migrate() signature per ↵Tim Graham
deprecation timeline.
2015-09-23Fixed #25453 -- Reworded makemigration's ask_not_null_alteration suggestion.Benjamin Wohlwend
2015-09-22Fixed #24509 -- Added Expression support to SQLInsertCompilerAlex Hill
2015-09-21Fixed #24921 -- set_autocommit(False) + ORM queries.Aymeric Augustin
This commits lifts the restriction that the outermost atomic block must be declared with savepoint=False. This restriction was overly cautious. The logic that makes it safe not to create savepoints for inner blocks also applies to the outermost block when autocommit is disabled and a transaction is already active. This makes it possible to use the ORM after set_autocommit(False). Previously it didn't work because ORM write operations are protected with atomic(savepoint=False).
2015-09-21Documented "rel objects".Aymeric Augustin
Kept the docstring short because these objects aren't very well defined and they're in the crosshairs of several refactorings.
2015-09-21Renamed descriptor classes for related objects.Aymeric Augustin
The old names were downright confusing. Some seemed to mean the opposite of what the class actually did. The new names follow a consistent nomenclature: (Forward|Reverse)(ManyToOne|OneToOne|ManyToMany)Descriptor. I mentioned combinations that do not exist in the docstring in order to help people who would search for them in the code base.
2015-09-21Added comments in related instances descriptors.Aymeric Augustin
2015-09-21Documented related models descriptors.Aymeric Augustin
Changed the poll / choices example to a more obvious parent / children. I think that reduces the cognitive load.
2015-09-21Fixed #22341 -- Split django.db.models.fields.related.Aymeric Augustin
At 2800 lines it was the largest module in the django package. This commit brings it down to a more manageable 1620 lines. Very small changes were performed to uniformize import style.
2015-09-21Fixed #24629 -- Unified Transform and Expression APIsJosh Smeaton
2015-09-19Fixed #25296 -- Prevented model related object cache pollution when create() ↵Raphael Merx
fails due to an unsaved object.
2015-09-19Fixed #25160 (again) -- Moved data loss check on reverse relations.Aymeric Augustin
Moved data loss check when assigning to a reverse one-to-one relation on an unsaved instance to Model.save(). This is exactly the same change as e4b813c but for reverse relations.
2015-09-19Fixed #24743, #24745 -- Optimized migration plan handlingMarkus Holtermann
The change partly goes back to the old behavior for forwards migrations which should reduce the amount of memory consumption (#24745). However, by the way the current state computation is done (there is no `state_backwards` on a migration class) this change cannot be applied to backwards migrations. Hence rolling back migrations still requires the precomputation and storage of the intermediate migration states. This improvement also implies that Django does not handle mixed migration plans anymore. Mixed plans consist of a list of migrations where some are being applied and others are being unapplied. Thanks Andrew Godwin, Josh Smeaton and Tim Graham for the review as well as everybody involved on the ticket that kept me looking into the issue.
2015-09-18Fixed #25417 -- Added a field check for invalid default values.Simon Charette
2015-09-18Fixed #24636 -- Added model field validation for decimal places and max digits.Iulia Chiriac
2015-09-18Refs #17785 -- Made docstring for sqlite3's get_relations() consistent with ↵Hynek Cernoch
other backends.
2015-09-17Refs #14091 -- Fixed connection.queries on SQLite.Aymeric Augustin
2015-09-17Removed the unused JoinPromoter.outer_votes attribute.Simon Charette
2015-09-17Refs #24215 -- Fixed Python 3.5 compatiblity for unhandled lazy ops error.Tim Graham
2015-09-14Fixed #25377 -- Changed Count queries to execute COUNT(*) instead of COUNT('*').Adam Chainz
2015-09-14Fixed #25393 -- Fixed MySQL crash when adding text/blob field with ↵Ville Skyttä
unhashable default.
2015-09-12Fixed #23395 -- Limited line lengths to 119 characters.Dražen Odobašić
2015-09-12Refs #24919 -- Raised more helpful error message for disabled migrationsMarkus Holtermann
2015-09-12Fixed #24919 -- Allowed disabling of migrations on a per app basisMarkus Holtermann
2015-09-11Fixed #25329 -- Prevented _nodb_connection from being left openAdam Chainz
2015-09-10Enabled parallel testing by default in runtests.py.Aymeric Augustin
2015-09-09Changed database connection duplication technique.Aymeric Augustin
This new technique is more straightforward and compatible with test parallelization, where the effective database connection settings no longer match settings.DATABASES.
2015-09-09Cloned databases for running tests in parallel.Aymeric Augustin
2015-09-07Refs #24215 -- Improved error message for unhandled lazy model operations.Alex Hill
2015-09-07Fixed typos in django/db/models/query.py docstrings.Nick Pope
2015-09-05Updated references to the TEST_* database settings.Aymeric Augustin
They were removed in Django 1.9. I could leave the reference to TEST_DEPENDENCIES in the 1.2.4 release notes because the link points to the right location and the name was accurate at the time.
2015-09-05Fixed #24525 -- Fixed AssertionError in some complex queries.Tim Graham
Thanks Anssi Kääriäinen for providing the solution.
2015-09-04Fixed #19263 -- Fixed crash when filtering using __in and an empty QuerySet.Tim Graham
Thanks Marcin Biernat for the initial patch and tests.
2015-09-03Fixed #25058 -- Added GenericRelations with related_query_name to the ↵sarthakmeh
admin's delete confirmation page.
2015-09-03Fixed #25335 -- Fixed regression where QuerySet.iterator() didn't return an ↵Gavin Wahl
iterator.
2015-09-01Removed obsolete TODO about moving CommaSeparatedIntegerField into contrib.Tim Graham
2015-09-01Fixed #25320 -- Reverted ManyToManyField.null to False for backwards ↵Tim Graham
compatibility. Thanks Tom Christie for the report and review.
2015-08-31Fixed #25331 -- Removed trailing blank lines in docstrings.Maxime Lorant
2015-08-31Fixed #25259 -- Added comments to header of generated migration filesTyson Clugg
2015-08-31Fixed #25252 -- Added friendly error message on incorrect .select_related() useY3K
Using select_related() after .values() or .values_list() is not possible because .values() or .values_list() already got the values they need.
generated by cgit v1.3 (git 2.53.0) at 2026-07-10 23:14:42 +0000