django.git/tests/backends/postgresql/test_compilation.py, branch maindjango
http://cgit.adnoto.dev/django.git/atom?h=main2025-12-31T15:41:55ZRefs #33647 -- Fixed silent data truncation in bulk_create on Postgres.2025-12-31T15:41:55ZSimon Charettecharette.s@gmail.com2025-12-23T06:25:56Zurn:sha1:d6ae2ed868e43671afc4d433c3d8f4d27f7eb555
Regression in a16eedcf9c69d8a11d94cac1811018c5b996d491.
The UNNEST strategy is affected by the same problem bulk_update has wrt/
to silent data truncation due to its usage of db_type which always returns
a parametrized subtype.
Fixed #36502 -- Restored UNNEST strategy for foreign key bulk inserts on PostgreSQL.2025-07-10T16:33:00ZSimon Charettecharette.s@gmail.com2025-07-10T16:33:00Zurn:sha1:0fe218842e0e396e3ab3982bd21227968a9e7fd8
Regression in 764af7a3d6c0b543dcf659a2c327f214da768fe4.Fixed #36088 -- Avoided unnecessary DEFAULT usage on bulk_create().2025-02-01T17:43:10ZSimon Charettecharette.s@gmail.com2024-12-09T23:38:18Zurn:sha1:4608d34b346c28d5d227363c881d3279378f40b3
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 #35936 -- Used unnest for bulk inserts on Postgres when possible.2024-12-11T12:56:18ZSimon Charettecharette.s@gmail.com2024-11-17T05:30:00Zurn:sha1:a16eedcf9c69d8a11d94cac1811018c5b996d491
This should make bulk_create significantly faster on Postgres when provided
only literal values.
Thanks James Sewell for writing about this technique, Tom Forbes for
validating the performance benefits, David Sanders and Mariusz Felisiak
for the review.