> What about calling the attribute something like "constraints" similar to > how it's done in SQLAlchemy [1]? For now the attribute can just contain a > list of Index() instances but that would also lay grounds for supporting > check constraints and other related table level options. > Since we are just allowing instances of Index class and it's subclasses right now, I don't think there is much gain in naming it "constraints". It might even confuse the user.
-- 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 post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/090de3a1-63da-4897-9bb6-a7997a9b9610%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
