chango.git - django

Age	Commit message (Collapse)	Author
2025-12-31	Refs #33647 -- Fixed silent data truncation in bulk_create on Postgres.	Simon Charette
	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.
2025-07-10	Fixed #36502 -- Restored UNNEST strategy for foreign key bulk inserts on ↵	Simon Charette
	PostgreSQL. Regression in 764af7a3d6c0b543dcf659a2c327f214da768fe4.
2025-02-01	Fixed #36088 -- Avoided unnecessary DEFAULT usage on bulk_create().	Simon Charette
	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.
2024-12-11	Fixed #35936 -- Used unnest for bulk inserts on Postgres when possible.	Simon Charette
	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.