#27627: OneToOneField doesn't allow multiple records with NULL value on
Microsoft
SQL Server
-------------------------------------+-------------------------------------
Reporter: Ryan Schave | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version:
(models, ORM) |
Severity: Normal | Resolution: invalid
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 Tim Graham):
* cc: Michael Manfre (added)
* status: new => closed
* resolution: => invalid
Comment:
It looks like removing `supports_nullable_unique_constraints = False` may
already yield a regression test in `tests/one_to_one/tests.py` due to the
usage of the feature flag there. Maybe other backends like `django-mssql`
would want to fix the issue so we could remove that feature?
--
Ticket URL: <https://code.djangoproject.com/ticket/27627#comment:6>
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/066.33ad03037258d2162946d42060618635%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
