The question is how we guess that it fits 80% of all use cases :) IMHO 80% are covered with the two approaches that I listed in the first mail.
I mean you reach the limits of the ORM pretty quickly as well but you can always drop down to raw Sql and circumvent the built in API restrictions On 06/13/2017 07:00 PM, James Bennett wrote: > Generally, I'd like to see something satisfying the needs of around 80% of > use cases out of the box before including it directly in Django. No > database-translation tool I'm aware of is even close to that level. > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/5c017ab6-93ce-6f4a-b38c-2c3b2696213a%40gmail.com. For more options, visit https://groups.google.com/d/optout.
