django.git/tests/bulk_create, branch fix-31295

Fixed #36702 -- Made bulk_create() return pk values set by an expression.

2025-11-06T16:58:01Z

Fixed IntegrityError in bulk_create.tests.BulkCreateTransactionTests due to duplicate primary keys.

2025-10-24T14:33:40Z

Some tests in BulkCreateTransactionTests were inserting Country objects with hardcoded primary keys, which could conflict with existing rows (if the sequence value wasn't bumped by another test). Updated the tests to dynamically select an unused primary key instead. Thanks to Simon Charette for the exhaustive and enlightening review.

Fixed failing bulk_create test raising IntegrityError when run in reverse.

2025-08-21T15:25:57Z

When running the `bulk_create` tests with Postgres settings and `--reverse`, the following IntegrityError was raised in bulk_create.tests.BulkCreateTransactionTests.test_objs_with_and_without_pk: django.db.utils.IntegrityError: duplicate key value violates unique constraint "bulk_create_country_pkey" DETAIL: Key (id)=(1) already exists. This branch fixes this by ensuring the ID is unique since DB sequences are not resetted between tests.

Avoided usage of DEBUG setting override in bulk_create tests.

2025-08-15T08:45:02Z

Asserting an upper bound for the number of executed queries can be achieved by using CaptureQueriesContext instead of enabling the whole DEBUG machinery.

Fixed #36490 -- Avoided unnecessary transaction in bulk_create.

2025-08-15T08:45:02Z

When dealing with an heterogeneous set of object with regards to primary key assignment that fits in a single batch there's no need to wrap the single INSERT statement in a transaction.

Refs #36143 -- Tested bulk_batch_size limit for bulk_update and bulk_create.

2025-05-08T10:37:11Z

Refs #36088, Refs #36260 - Added supports_expression_defaults checks in bulk_create() tests.

2025-04-05T16:47:53Z

Fixed #36260 -- Made bulk_create() work with DB-generated primary keys.

2025-03-26T08:55:09Z

Co-authored-by: Simon Charette

Fixed #36088 -- Avoided unnecessary DEFAULT usage on bulk_create().

2025-02-01T17:43:10Z

When all values of a field with a db_default are DatabaseDefault, which is the case most of the time, there is no point in specifying explicit DEFAULT for all INSERT VALUES as that's what the database will do anyway if not specified. In the case of PostgreSQL doing so can even be harmful as it prevents the usage of the UNNEST strategy and in the case of Oracle, which doesn't support the usage of the DEFAULT keyword, it unnecessarily requires providing literal db defaults. Thanks Lily Foote for the review.

Fixed #34698 -- Made QuerySet.bulk_create() retrieve primary keys when updating conflicts.

2023-07-10T11:17:28Z