#27627: OneToOneField doesn't allow multiple records with NULL value on
Microsoft
SQL Server
-------------------------------------+-------------------------------------
Reporter: Ryan Schave | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version:
(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
-------------------------------------+-------------------------------------
Comment (by Ryan Schave):
It makes sense that the 3rd party backend should handle this. There is
already an open pull request (https://github.com/michiya/django-pyodbc-
azure/pull/43) for django-pyodbc-azure.
Would it be beneficial to submit the test that passes with the supported
backends and fails with the the django-pyodbc-azure backend? This would
at least give visuality into the problem when Django tests are run against
that backend.
--
Ticket URL: <https://code.djangoproject.com/ticket/27627#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 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/066.e236af5316e9618825dcb5fbcbc2bc0f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
