Changes between Version 5 and Version 6 of Ticket #30913
- Timestamp:
- Oct 26, 2019, 4:48:07 PM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #30913 – Description
v5 v6 29 29 One of the biggest possibilities of this feature is to add included columns to unique indexes and use them to perform Index Only Scans. This would require adding the same kwarg to `UniqueConstraint`. The implementation would be a lot like the `condition` kwargs to both `Index` and `UniqueConstraint`. 30 30 31 At the moment the only Django-supported database that can use this feature is Postgres but it's also supported by Microsoft SQL Server and IBM Db2 with the same syntax. Because if this I think it shouldn't be implemented as a postgres only feature but exposed on `BaseDatabaseSchemaEditor` to ease the adding of support when/if sqlite or mariadb adds support.31 At the moment the only Django-supported database that can use this feature is Postgres but it's also supported by Microsoft SQL Server and IBM Db2 with the same syntax. Because of this I think it shouldn't be implemented as a postgres only feature but exposed on `BaseDatabaseSchemaEditor` to ease the adding of support when/if sqlite or mariadb/mysql get it. 32 32 33 33 I have a proof of concept I'm working on and will create a PR soon if accepted.