--
Ticket URL: <https://code.djangoproject.com/ticket/32780>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* has_patch: 0 => 1
Comment:
PR: https://github.com/django/django/pull/14444
--
Ticket URL: <https://code.djangoproject.com/ticket/32780#comment:1>
* needs_better_patch: 0 => 1
* type: Bug => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
> stating that a constraint won't be created even though it is.
That's not true, a constraint won't be created. However I agree that
remaking table is not necessary and we can make it a noop. We can do the
same for deferrable unique constraints.
--
Ticket URL: <https://code.djangoproject.com/ticket/32780#comment:2>
Comment (by Hannes Ljungberg):
> That's not true, a constraint won't be created. However I agree that
remaking table is not necessary and we can make it a noop. We can do the
same for deferrable unique constraints.
Ah! I just assumed that the table would be recreated with the constraint.
Thanks for clearing that up!
--
Ticket URL: <https://code.djangoproject.com/ticket/32780#comment:3>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"3e0fdf5546b8e172c87f255d55c6ddbe7d69f365" 3e0fdf5]:
{{{
#!CommitTicketReference repository=""
revision="3e0fdf5546b8e172c87f255d55c6ddbe7d69f365"
Fixed #32780 -- Made Add/RemoveConstraint operations a noop for
covering/deferrable unique constraints on SQLite.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32780#comment:4>