Perhaps it's just me, but I've very rarely wanted a SlugField that wasn't unique. Would this not be a sensible default? I realise that a lot of apps will rely upon this default, but objectively speaking would this not be better? Perhaps this change would be appropriate for django 2.0.
At the moment, slug = models.SlugField()creates a non-unique field, and if you want it to be unique, then you must add unique=True. I feel this is wrong. It seems to me that unique should be default, and if you don't want a unique slug, you should explicitly state that: slug = models.SlugField(unique=False) I've added an issue on the tracker for this: https://code.djangoproject.com/ticket/18525 I realise this may be a contentious issue...or that I may even get shot down in flames on this one ;P Go easy on me! :) What do you all think? Charlie. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/wb1YDBfDUO4J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
