Re:Waiting for PostgreSQL 14 – SEARCH and CYCLE clauses
by touisteur on Thursday February 04, 2021 @11:13AM
(#26026667)
Never use inheritance at all?
I was thinking you could reconstruct part of the app stack by observing and clustering the requests and transactions. But then some people think join is the devil and you'd be back to square one. In a perfect world every app would have only views over what they need and prepared requests. But then CI/CD and all kind of tests can become very painful...
Re:Waiting for PostgreSQL 14 – SEARCH and CYCLE clauses
by eyelidlessness on Thursday February 04, 2021 @10:10PM
(#26032620)
Django is just plain bad at data modeling there I said it
Re:Waiting for PostgreSQL 14 – SEARCH and CYCLE clauses
by ttz on Thursday February 04, 2021 @11:16PM
(#26033045)
I don't know you, but I think we'd be great friends based solely on this statement.
Re:Waiting for PostgreSQL 14 – SEARCH and CYCLE clauses
by eyelidlessness on Friday February 05, 2021 @12:52AM
(#26033547)
I don’t make friends as easily as hating on any technology but I do make friends easily on kindness. Hi! I learned a lot great and not great working with DRF. Kind of took it and ran with it on TypeScript and Node. Working on a much better HTTP interface for that platform.
My favorite /s is the table with a single column containing the id of the record itself.
It's basically impossible to start from the database and understand what's going on. It will be a huge pain to interface to this database from something else.
On the other side, I'm maintaining another Django app for the same customer, with saner tables (no inheritance) and that's on par with other ORMs.
My take is never use inheritance with Django.