Hi everyone,
In our company, we also use the ability to define our own indexes, but with
the current implementation of base Index class, we basically need to copy
several methods entirely from it.
What do we want is implement UNIQUE indexes with the UPPER function wrapper
around field names [1].
T
I did a similar thing (but only tested in postgres) a while back, using Q's
/ filter clause to generate the where clause.
Perhaps with our powers combined we're close to a generalised
implementation?
https://github.com/ashleywaite/django-more/blob/master/django_more/indexes.py
On Saturday, O
It looks to me that the same trick on Oracle can be used on MySQL/MariaDB -
indexing a generated column. There's a comment on
https://mariadb.com/kb/en/library/generated-columns/ to that effect.
P.S. Drizzle is long dead, the site isn't even up any more :)
On 8 October 2017 at 12:38, Tim Allen w
I would love to see partial indexes supported. Great work! As far as
databases with Django support:
- PostgreSQL supports partial indexes
- SQLite supports partial indexes
- SQL Server supports them, called "filtered indexes"
- Oracle: Sort of supports
them: https://blog.jooq.org/2017/01/18/how-
Hi django-developers,
I have written a package that implements PostgreSQL and SQLite partial
indexes on top of the new class-based
indexes: https://github.com/mattiaslinnap/django-partial-index
The most common use case is partial unique constraints, but I have a few
projects where non-unique pa
