#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):
I can produce a test that passes w/ SQLite and PostgreSQL, but fails with
MS SQL. I assume since MS SQL is not a built-in backend, there is little
that can be done easily on the Django side and my experience w/ MS
suggests they aren't going to address this. I created a custom migration
that removes the constraint added by the initial Django migration and add
a unique index that allows multiple NULLs.
I assume that the code in django/db/migrations works together with the
appropriate backend in django/db/backends. Does Django use the base
backend when a 3rd party database is used?
--
Ticket URL: <https://code.djangoproject.com/ticket/27627#comment:3>
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.ab9603eb29412496e6f2c969cf2855fd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
