#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: (none)
Type: Bug | Status: new
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* cc: Simon Charette (added)
Comment:
> Then would we want to modify the test logic and add
@skipUnlessDBFeature("can_return_columns_from_insert")?
Adding the skipUnlessDBFeature shouldn't be necessary as we expect it to
work for all backends, regardless of whether
can_return_columns_from_insert is True or False
I don't know what the fix should be but I recently reviewed #36490 and
Simon had a few ideas around improving `bulk_create`, so I would be
interested to hear his thoughts here
--
Ticket URL: <https://code.djangoproject.com/ticket/36550#comment:10>
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/01070198ace5a699-389bea92-5e75-421b-811e-49ad35ad7410-000000%40eu-central-1.amazonses.com.
