#17467: compare id of Site object with SITE_ID before updating (in
create_test_db)
-------------------------------------+-------------------------------------
Reporter: kallous@… | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.3
(models, ORM) | Resolution:
Severity: Release blocker | Triage Stage: Design
Keywords: | decision needed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* severity: Normal => Release blocker
* stage: Accepted => Design decision needed
Comment:
Currently, Django allows forcing the primary key of an object — that's
what #17415 is about — so, even if we rollback the offending code, it's a
limitation of django-mssql.
I'm marking this as a release blocker, because it is a regression from the
previous version, and it's a blocker for your (legitimate) use case.
But I really can't say what's the best solution. We're stuck by SITE_ID, a
mandatory setting.
--
Ticket URL: <https://code.djangoproject.com/ticket/17467#comment:5>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.