Django-mssql would skip all of theses tests due to
{{{can_distinct_on_fields = False}}}, but it throws a database exception
during setUp when it tries to insert multiple NULLs for the
'''greatest_fan''', nullable, unique field.
--
Ticket URL: <https://code.djangoproject.com/ticket/21636>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
https://github.com/django/django/pull/2090
--
Ticket URL: <https://code.djangoproject.com/ticket/21636#comment:1>
* status: new => closed
* resolution: => wontfix
Comment:
PR was accidentally made against 1.6.x. This is likely a non-issue with
master because the '''can_distinct_on_fields''' check was bumped up to the
class, instead of on each of the tests. None of the known database
backends support '''can_distinct_on_fields''', but not
'''ignores_nulls_in_unique_constraints''' in such a way that causes an
error during setUp.
--
Ticket URL: <https://code.djangoproject.com/ticket/21636#comment:2>