Refs #36416, #34378, #36143 -- Fixed isolation of LookupTests.test_in_bulk_preserve_ordering_with_batch_size(). #19532
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
max_query_params
is a property on SQLite since ticket-36143 (6.0), so the test for ticket-34378 must patch the class.This was exposed via a poor interaction with the test for ticket-36416 (backported to 5.2, but rewritten in #19522 for 6.0, ticket-36430).
To reproduce the failure on postgres, here is a django-docker-box invocation:
No need to backport, since
max_query_params
is a property only on main. However, I think this change still brings value separately from #19522: if you adjusttest_in_bulk_preserve_ordering_with_batch_size()
to run on SQLite by removing the skip decorator, you see: