#36064: save() behavior for new model instance with default primary key does not
apply to CompositePrimaryKey
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: dev
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Csirmaz Bendegúz):
Replying to [comment:2 mao xin chen]:
> This is my first time trying to submit code. Please see if it can meet
the requirements. If so, I will learn to submit PR. Thanks
Thanks for the patch! Please check the
[https://docs.djangoproject.com/en/dev/internals/contributing/ docs] on
how to contribute. If you open a PR on GitHub we can review your code.
--
Ticket URL: <https://code.djangoproject.com/ticket/36064#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701943fc33ad5-9bbe4c52-79a8-4096-9d04-7a7097ebb9ad-000000%40eu-central-1.amazonses.com.
