←back to thread

Django: what’s new in 6.0

(adamj.eu)
378 points rbanffy | 2 comments | 09 Dec 25 20:33 UTC | HN request time: 0.876s | source
Show context
aynyc ◴[10 Dec 25 13:47 UTC] No.46217665[source]▶
I've been using Django on and off at work for the past few years. I really like it. That being said, I still find its ORM difficult. I understand it now that since it's an opinionated framework, I need to follow Django way of thinking. The main issue is that at work, I have multiple databases from different business units. So I constantly have to figure out a way to deal with multiple databases and their idiosyncrasies. I ended up doing a lot of hand holding by turning off managed, inspectdb and then manually delete tables I don't want to show via website or other reasons. For green webapps we have, django is as good as it gets.
replies(6): >>46217950 #>>46218252 #>>46218271 #>>46218403 #>>46218484 #>>46218923 #
1. JodieBenitez ◴[10 Dec 25 14:44 UTC] No.46218252[source]▶
Do you use Django's multiple databases support ? (https://docs.djangoproject.com/en/6.0/topics/db/multi-db/)
replies(1): >>46219887 #
2. aynyc ◴[10 Dec 25 16:38 UTC] No.46219887[source]▶
Yes, we have to in order to use a lot of the features. The core issue for us is really the way Django assumes code represents database state. In normal webapp where the application has full control of the database, that's a good idea. But our databases are overloaded for simple transactions, analytics, users managements, jobs and AI. Business uses the databases in various ways such as Power BI, Aquastudio, etc.. Django app is actually a tiny part of the database. As you can imagine, we duck tape the heck out of the databases, and Django goes bonkers when things aren't matching.