On Sunday, February 28, 2016 at 11:33:16 AM UTC+1, Loïc Bistuer wrote: > > I don't think this is a problem, we could validate that the backend > supports it during save then blow up if we detect it doesn't. I think we do > that for truncation on MySQL. If the model specifies something that the db > doesn't support it's a configuration problem, not a user validation > problem. >
I do not see how blowing up on save is a good idea (especially not if we ran model validation before). We do not do that for MySQL (at least not if your project is configured properly, leaving issues with utf8mb4 out for now) since our model form validation is able to use the supplied max_length to inform the user that the data is invalid __before__ save. -- 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/23ce2d62-45ed-48f7-9fc1-bc1eb4c47ef8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
