As proposed by timgraham in https://code.djangoproject.com/ticket/24507 I
open the discussion here.
When adding db_index=True on a CharField Django automatically create 2
indexes on some backends as PostgreSQL. But in usage the second index is
not always necessary if you never use contains() or
Hi Alex and Marc,
Alex thanks for your answer, to be clear I did not open the discussion to
find a solution to resolve my problems, they are done. My goal is to open
discussion on indexes support in Dango. And as you right said, the solution
is effectively to not create indexes in the models an
Hi,
Be aware I will never speak about Django application as often used in
Django developpement, here the string **application_name** is not the name
of a Django'app.
PostgreSQL permits on connection to specify a string that represent the
name of application that connect, useful to identify huma
Thanks Andriy, I missed that, is this new in 1.8 ?
Le lundi 22 juin 2015 17:06:46 UTC+2, Andriy Sokolovskiy (coldmind) a
écrit :
>
> I think due to
> https://github.com/django/django/blob/8047e3666b0b50bb04e6f16c2a4fb21ddfd5713f/django/db/backends/postgresql_psycopg2/base.py#L162
>
> you can s
