summaryrefslogtreecommitdiff
path: root/tests/select_for_update
AgeCommit message (Collapse)Author
2020-08-11Fixed #31866 -- Fixed locking proxy models in QuerySet.select_for_update(of=()).Daniel Hillier
2020-05-21Fixed #30375 -- Added FOR NO KEY UPDATE support to ↵Manuel Weitzman
QuerySet.select_for_update() on PostgreSQL.
2020-02-11Fixed #31246 -- Fixed locking models in QuerySet.select_for_update(of=()) ↵Abhijeet Viswa
for related fields and parent link fields with multi-table inheritance. Partly regression in 0107e3d1058f653f66032f7fd3a0bd61e96bf782.
2019-12-02Fixed #30953 -- Made select_for_update() lock queryset's model when using ↵Mariusz Felisiak
"self" with multi-table inheritance. Thanks Abhijeet Viswa for the report and initial patch.
2019-04-29Fixed Python PendingDeprecationWarning in select_for_update.tests.Jon Dufresne
2018-11-21Fixed #29949 -- Refactored db introspection identifier converters.Mariusz Felisiak
Removed DatabaseIntrospection.table_name_converter()/column_name_converter() and use instead DatabaseIntrospection.identifier_converter(). Removed DatabaseFeatures.uppercases_column_names. Thanks Tim Graham for the initial patch and review and Simon Charette for the review.
2017-12-26Fixed #28944 -- Fixed crash when chaining values()/values_list() after ↵Ran Benita
QuerySet.select_for_update(of=()).
2017-10-28Refs #28010 -- Allowed reverse related fields in SELECT FOR UPDATE .. OF.Ran Benita
Thanks Adam Chidlow for polishing the patch.
2017-08-16Fixed #28498 -- Fixed test database creation with cx_Oracle 6.Mariusz Felisiak
2017-07-29Used assertRaisesMessage() to test Django's error messages.Mads Jensen
2017-06-29Fixed #28010 -- Added FOR UPDATE OF support to QuerySet.select_for_update().Ran Benita
2017-04-11Updated docs after changing select_for_update() to raise NotSupportedError.Ran Benita
Follow up to 054a44d6f0f75395bd02a21e31ea904a24750a2b.
2017-04-10Used NotSupportedError instead of DatabaseError in SQLCompiler.as_sql().Mariusz Felisiak
2017-04-07Fixed #23147 -- Disabled a limit/offset on a query with select_for_update on ↵Mariusz Felisiak
Oracle. Thanks Shai Berger and Tim Graham for the reviews.
2017-01-20Refs #23919 -- Removed django.test.mock Python 2 compatibility shim.Tim Graham
2017-01-18Refs #23919 -- Removed encoding preambles and future importsClaude Paroz
2016-11-10Refs #27392 -- Removed "Tests that", "Ensures that", etc. from test docstrings.za
2016-10-04Fixed #27193 -- Preserved ordering in select_for_update subqueries.François Freitag
2016-09-09Fixed #27062 -- Eased implementing select_for_update() on MSSQL.Mikhail Denisenko
2016-08-08Refs #22343 -- Corrected a test for missing select_for_update(nowait=True) ↵Simon Charette
support.
2016-08-08Fixed #26500 -- Added SKIP LOCKED support to select_for_update().Simon Charette
Thanks Tim for the review.
2016-08-05Used CaptureQueriesContext in select_for_update tests.Simon Charette
2016-01-29Refs #26022 -- Used context manager version of assertRaises in tests.Hasan
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-02-06Sorted imports with isort; refs #23860.Tim Graham
2015-01-28Removed threading fallback imports.Tim Graham
Django imports threading in many other places without fallback.
2014-12-01Replaced router.routers usage with override_settings(DATABASE_ROUTERS); refs ↵wrwrwr
#23933.
2014-08-05Fixed #23061: Avoided setting a limit on a query for get with ↵Shai Berger
select_for_update on Oracle Thanks Michael Miller for reporting the issue.
2014-04-10Fixed #22343 -- Disallowed select_for_update in autocommit modeShai Berger
The ticket was originally about two failing tests, which are fixed by putting their queries in transactions. Thanks Tim Graham for the report, Aymeric Augustin for the fix, and Simon Charette, Tim Graham & Loïc Bistuer for review.
2014-03-21Removed legacy transaction management per the deprecation timeline.Aymeric Augustin
2013-12-23Imported override_settings from its new location.Aymeric Augustin
2013-11-02Fixed #21302 -- Fixed unused imports and import *.Tim Graham
2013-10-23Fixed #21298 -- Fixed E301 pep8 warningsAlasdair Nicol
2013-10-21Removed some direct settings manipulations in tests; refs #21230.Bouke Haarsma
2013-10-19Removed unused local variables in tests.Tim Graham
2013-10-18Fixed #21287 -- Fixed E123 pep8 warningsAlasdair Nicol
2013-09-24Isolated select_for_update tests a bit more.Florian Apolloner
This change prevents including the multiple_database test models without duplicating the router code (we probably should do this at one point). Refs #21148
2013-09-09Removed unneeded imports in tests's __init__.py and unified them.Florian Apolloner
2013-08-06Fixed #19918 -- Modified select_for_update to run on the write database.Alex Cucu
2013-07-29Removed most of absolute_import importsClaude Paroz
Should be unneeded with Python 2.7 and up. Added some unicode_literals along the way.
2013-07-14Fixed #20746 -- Removed Python 2.6 specific code/docsTim Graham
2013-07-01Stopped using django.utils.unittest in the test suite.Aymeric Augustin
Refs #20680.
2013-06-10Defined available_apps in relevant tests.Aymeric Augustin
Fixed #20483.
2013-03-11Made transaction.managed a no-op and deprecated it.Aymeric Augustin
enter_transaction_management() was nearly always followed by managed(). In three places it wasn't, but they will all be refactored eventually. The "forced" keyword argument avoids introducing behavior changes until then. This is mostly backwards-compatible, except, of course, for managed itself. There's a minor difference in _enter_transaction_management: the top self.transaction_state now contains the new 'managed' state rather than the previous one. Django doesn't access self.transaction_state in _enter_transaction_management.
2013-03-06Used more precise test assertions.Aymeric Augustin
2013-02-27Fixed #19861 -- Transaction ._dirty flag improvementAnssi Kääriäinen
There were a couple of errors in ._dirty flag handling: * It started as None, but was never reset to None. * The _dirty flag was sometimes used to indicate if the connection was inside transaction management, but this was not done consistently. This also meant the flag had three separate values. * The None value had a special meaning, causing for example inability to commit() on new connection unless enter/leave tx management was done. * The _dirty was tracking "connection in transaction" state, but only in managed transactions. * Some tests never reset the transaction state of the used connection. * And some additional less important changes. This commit has some potential for regressions, but as the above list shows, the current situation isn't perfect either.
2013-02-26Merged regressiontests and modeltests into the test root.Florian Apolloner