On Sat, Oct 24, 2015 at 5:42 AM, Marc Tamlyn <marc.tam...@gmail.com> wrote:
> I disagree with this system check and I would like to see it reverted > before 1.9 final. > I agree - I’d argue that this check is demonstrably *incorrect*. > I admit that my opinions here are skewed by the fact that I think model > level validation is fundamentally not well implemented by Django at all. I > work to a philosophy that there are two places where validation happens - > once at the entry point to the system (form or serialiser) and once at the > database level to ensure integrity of the data. > I don’t think you even need to bring model validation into this discussion - the two keywords in play here (blank and default) are for entirely different parts of Django. blank is display/form logic. default is model logic. There’s some crossover to be sure, but the use case presented by James is entirely legal and valid for exactly that reason. So, +1 - this should be reverted. As far as I can make out, it’s not even correct to say that this is a warning - the model description makes perfect sense as-is. The only way I can see that this check would be valid is a confirmation of blank=False and a model-level non-zero length validator - but that’s getting sufficiently eclectic that I don’t think it warrants inclusion. Yours, Russ Magee %-) -- 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq84_4oy2aGEP7EJ7AJCWDeuEw0OFrZafj6HQ%2BW1QRnEoWvw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
