#30362: Partial indexes and check constraints crash when inherited from abstract
models.
-------------------------------------+-------------------------------------
Reporter: Tim Dawborn | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: inheritance index | Triage Stage: Accepted
name |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Dawborn):
Replying to [comment:4 Ian Foote]:
> A check seems sensible to me, as does documentation. I'm less sure about
the callable idea, but it could work.
Well, what I'd actually like is to not have to specify the index name, and
let Django construct it like it does index names for Index's that don't
contain conditions. The callable suggestion was a work around for having
to explicitly specify a name.
Can I ask what the motivation for explicitly requiring an index name was
when providing a condition?
--
Ticket URL: <https://code.djangoproject.com/ticket/30362#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 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/068.1bce02b62e72c971e4780c13f859e27b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
