#27118: Make QuerySet.get_or_create()/update_or_create() error for a non-field in defaults -------------------------------------+------------------------------------- Reporter: brighters | Owner: nobody Type: | Status: new Cleanup/optimization | Component: Database layer | Version: 1.9 (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 timgraham):
* needs_better_patch: => 0 * needs_tests: => 0 * needs_docs: => 0 * type: Bug => Cleanup/optimization * stage: Unreviewed => Accepted Comment: Raising an error will be backwards-incompatible, but I think it's more likely to reveal bugs than to cause a problem for a legitimate use case. If pre-release testing reveals otherwise, we could reconsider. -- Ticket URL: <https://code.djangoproject.com/ticket/27118#comment:1> 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 post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/067.764e37b3ea8304e470aad2dac3a43fed%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.