I agree - #24082 is unrelated since it's PostgresSQL and text field
specific, presumably resulting from:
https://github.com/django/django/blob/8eb56f3c786b4dd7f78a60145ae2e483e24b62c1/django/db/backends/postgresql/schema.py#L34-L48
The issue in this thread is specific to the interaction between
I think that the issue on Trac is actually something different, it talks
about the need (or not) of an index, when defining a unique constraint.
Most databases (if not all) will create an index automatically when a
unique constraint is defined, and correct me if I'm wrong, but PostgreSQL
(I
Did you try to find anything related in Trac? Maybe
https://code.djangoproject.com/ticket/24082?
I use this query in Google: postgresql unique index
site:code.djangoproject.com
On Friday, September 16, 2016 at 9:51:13 AM UTC-4, Dilyan Palauzov wrote:
>
> Hello,
>
> according to the
Hello,
according to the documentation models.ForeignKeys creates implicitly an index
on the underlying database.
Wouldn't it be reasonable to change the default behaviour to only create
implicit index, if there is no index_together or unique_together starting with
the name of the foreign
