> I am aware there are patterns to work around this in Django. My position is that skipping validation should be the rare edge case and not the easy naive path. Unless Django's stated purpose is to be a cute toy for making blogs, and robust infrastructure is off-label, but that's not what I see in the wild.
I think you're going a bit too far with your judgement and comparisons. It's already clear for everyone involved in this thread that you're firmly convinced that your way of doing things is the only right one. You don't need to emphasize it any more. I can say that in the past 15+ years I made dozens of web apps (I've never written a blog) including critical workflows for international retailers, pharmaceutical companies, public sector etc. and I've never missed auto-validation in the ORM layer. Is this an argument in the discussion? Not really, IMO :) It's just the way it is, it's not something that can or should convince anyone that I'm right :) Personally, I agree with James and I'm strongly against any auto-validation in the ORM. I'm also against extra settings and built-in subclasses of `Model` as `ValidatingModel`, because they would be confusing for newcomers and increase the barrier of entry for developers. Django has to make design decisions and that's one of them. 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/6303eaf5-f4d9-4c15-bcce-f57efc929d0bn%40googlegroups.com.
