4 ms·
This is very obvious. What part of your document editor needs to be backed by a relational database? Why use an MVT system if you don't need the Model part of
by busterarm 9mo ago
This is very obvious.
What part of your document editor needs to be backed by a relational database?
Why use an MVT system if you don't need the Model part of it?
- ffsm8 9mo agohttps://github.com/suitenumerique/docs/blob/main/src/backend/core/models.py https://github.com/suitenumerique/docs/blob/main/src/backend... I see, in your broad and experienced mind, document editors don't have users, permissions, and the whole document management itself, comments on lines/threads, reactions on comments Seriously, theyre all as cookie cutter perfect usecase for Django as you can get, but I guess you haven't actually thought about the domain and just wanted to take a dumb on other devs with intern-to-junior level insights
- busterarm 9mo agoYou don't necessarily need that to get these things...
- ffsm8 9mo agoObviously, you don't need the model abstraction for any software, ever. It is just more or less suited for a domain. And in this case, as would be obvious from thinking about it, the only part it's not suited for is the live syncing of the text edit on the frontend, which is one one small part of the whole.
- busterarm 9mo agoStoring the text documents themselves in a relational database is itself a terrible idea.
- ffsm8 9mo agoIt's not a bad idea, generally. it depends on the implementation. If you're updating it multiple times per second, then yes, it's a bad idea. Now go check if they're doing it or you're just suggesting from the dunning kruger symptom.