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 Marc,
Great, that's very interesting reading! A lot of similarities to what I had
in mind and a couple of differences.
As I imagine the API, Indexes would be backend-specific rather than
generic. Field would have a get_db_indexes() method which took a connection
as its first argument like get_
I have some plans (see https://github.com/django/deps/pull/6) to rework
more widely how indexes are managed and allow finer control over them. It
pretty much includes all the things mentioned by Alex. I'm intending on
doing some work on it over the next few weeks.
Marc
On 20 March 2015 at 02:27,
I agree that this is a problem, and I'd like to see more control over
indexes generally in Django.
However, at first glance I suspect that fixing only your problem would mean
adding special-case gunk to the Field class in addition to the Postgres
schema editor where it currently lives[1]. It fe
