Hi, This proposal is not really nice from a maintenance point of view as we will end with the same complicated situation we currently have with uniqueness checks or indexes i.e. many ways to define the same:
- Field.unique/index - Meta.unique_together/index_together - Meta.constraints/indexes It's especially error-prone in migrations and different database behavior on fields already covered by the same constraints/indexes. I'm pretty sure that we've introduced Meta.contraints/indexes to avoid this happening in the future, and we are rather leaning to leave only Meta.constraints/indexes and remove other options in the future. Not creating a new one. Initial -1 from me. Best, Mariusz -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/954af838-2176-4877-b4ac-70525cddcbf5n%40googlegroups.com.
