> Le 29 juil. 2015 à 18:25, Podrigal, Aron <ar...@guaranteedplus.com> a écrit :
> 
> I see models as what defines the database ddl and and not a representation 
> from a  end users perspective.

Django models do a bit more than this: see the `validators` argument, 
EmailField, etc.
> And I see the tight coupling between the 2 improper.

I understand your perspective; it's a trade-off between purity and convenience 
and the optimal answer depends on each project.
> For me I rarely use the builtin generated widgets, I use restframework so all 
> I'm interested in a model is for db definition in a highly customizable way.

Please make sure your proposals also account for the various way Django can be 
and has been used :-)

-- 
Aymeric.

-- 
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/2A451482-2DDD-42CE-895B-55E1FF1026D3%40polytechnique.org.
For more options, visit https://groups.google.com/d/optout.
  • Making... Podrigal, Aron
    • R... Loïc Bistuer
      • ... Tim Graham
        • ... Podrigal, Aron
          • ... Aymeric Augustin
            • ... Podrigal, Aron
    • R... Paulo Maciel
      • ... 'Tom Evans' via Django developers (Contributions to Django itself)
        • ... Christophe Pettus
          • ... Podrigal, Aron
            • ... Christophe Pettus
              • ... Podrigal, Aron
                • ... Christophe Pettus
                • ... Podrigal, Aron
                • ... Christophe Pettus

Reply via email to