News for hackers. Stuff that matters.

A comment on Removing Python 2.x support from Django for version 2.0. Parent comment

Re:Removing Python 2.x support from Django for version 2.0 by metaphorm on Thursday January 19, 2017 @11:01AM (#13436773)
> there are some rough corners

content_types, generic foreign keys, and basically any other uncommon use pattern for RDBMS are very rough in django. Tradeoff of their ORM being heavily streamlined for the 90% use cases (typical SQL selects and upserts).

[ Parent | on HN ]
Re:Removing Python 2.x support from Django for version 2.0 by rbistolfi on Thursday January 19, 2017 @11:11AM (#13436857)
But you can use other ORM if you want, or no ORM. However, the benefits of using Django come mostly from using their highly integrated components, I admit. In any case, we swapped the ORM with our own implementation of the data layer and we are doing fine. I like the API overall, specially class based views.
[ Parent | on HN ]
Re:Removing Python 2.x support from Django for version 2.0 by raverbashing on Thursday January 19, 2017 @11:16AM (#13436890)
Yes

Might be easier to just write SQL in those cases

[ Parent | on HN ]