4 ms·
>> I would stick to the most boring stack Just use sql. Very straightforward and easy to use program understand maintain.
by andrewstuart 2y ago
>> I would stick to the most boring stack
Just use sql. Very straightforward and easy to use program understand maintain.
- troupo 2y ago> Just use sql. Very straightforward and easy to use program understand maintain. In the end SQLAlchemy and Alembic generate and execute SQL. The weird behaviours are due to sqlite's idiosynchasies
- mbreese 2y agoI think this is the best advice. The further you are away from your data store, the more you are relying on the used cases others have considered. Just because a library needs features that something like SQLite doesn’t provide doesn’t mean that you need that feature. But every extra abstraction in your stack has this danger. I also think that the closer you are to your DB, more you appreciate the features you actually need are. A developer should know how their data is ultimately stored. And if an ORM hides this from you, that’s a problem. Note: and ORM doesn’t need to hide this and can be a rational way to manage DB storage. But it’s then up to the developer to manage that abstraction. I’ve done this before where I used an ORM but I still knew exactly what SQL was going to be generated. But for many, especially new devs, the ORM is a black box.