#36550: AssertionError raised when bulk creation model with primary key set via
pre_save (e.g. auto_now_add) on databases with
can_return_columns_from_insert
-------------------------------------+-------------------------------------
Reporter: Will-Ruddick | Owner:
| JaeHyuckSa
Type: Bug | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Abhimanyu Singh Negi):
Replying to [comment:16 Sarah Boyce]:
Hi Sarah, I see the last patch was more thatn 5 months earlier, and the
latest owner hasnt made any progress on it, so i would like to take up the
issue.
I plan to update the bulk_create preparation step so that primary key
values which can be determined locally are populated before objects are
partitioned, and so that classification checks whether all primary key
fields are actually filled rather than relying only on the existing check.
I’ll also extend or adjust the tests to ensure that bulk_create()
correctly handles primary keys set via pre_save(), both in memory and in
the database, and that the behavior remains consistent across supported
backends.
**
if this sounds okay assign me the issue or give permission to assign
myself.**
--
Ticket URL: <https://code.djangoproject.com/ticket/36550#comment:18>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019c6352a093-0971fa91-b416-43e4-908d-3e2dd7a80c3a-000000%40eu-central-1.amazonses.com.
