4 ms·

Being closer to SQL in my projects meant that it had more footguns than C++ and developers had to know a lot about DB details to not break things.

• bbkane 1y ago
  I don't think it's unreasonable that devs should have to learn about database details to correctly use a database. Could you list some specific examples where things broke because of SQLAlchemy's design?
  • izacus 1y ago
    Managing connections, connection looking and transactions was something that was always an issue with SQLalchemy for us. Migrations were significantly more terrible as well.
• lelanthran 1y ago
  The only footgun is pretending that using an ORM means not having to learn SQL.
  • codr7 1y ago
    Exactly! I like my ORMs based on SQL concepts, not OOP concepts. So you do have to know SQL, but you get more convenient ways of generating it. https://github.com/codr7/tyred https://github.com/codr7/tyred
  • izacus 1y ago
    That's not what I said though.