#28228: changing a primary key and saving results in a new object rather than
renaming the existing object.
-------------------------------------+-------------------------------------
Reporter: Chris | Owner: nobody
Withers |
Type: Bug | Status: new
Component: Database | Version: 1.11
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
See https://github.com/encode/django-rest-framework/issues/5158.
Incorrect behaviour in https://github.com/encode/django-rest-
framework/issues/5158#issuecomment-302679922.
Expected behaviour:
{{{#!python
MyModel.objects.all()
# <QuerySet [<MyModel: test>, <MyModel: test1>]>
instance = MyModel.objects.all()[0]
instance.name
# 'test'
instance.name = 'other test'
instance.save()
MyModel.objects.all()
# <QuerySet [<MyModel: test1>, <MyModel: other test>]>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28228>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/049.48db1fd1d32c16fa3e168fd6320a878a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
