4 ms·

There are plenty of good ORMs for Postgres if that's what floats your boat, but the advantage of Postgres is you can always drop down to SQL.

• dominotw 7y ago
  > but the advantage of Postgres is you can always drop down to SQL. All the project i've worked on eventually devolved into a weird mess of part orm and part SQL.
  • goatinaboat 7y ago
    Would have been easier and cleaner just to go with SQL from the start. Sadly devs always think it will be different if they try a different ORM next project and we always end up in the same place.
    • nicolaslem 7y ago
      As a developer working on projects using both approaches, it would be hard for me to pick a clear winner. One key difference for less experienced developers is that ORMs are usually integrated for you as part of a bigger framework (Django, Rails...). This provides some guidelines to get started on a more or less sane way. On the other hand plain SQL usually relies directly on the database client (or a thin layer like SQLAlchemy core) that requires you to make many decisions about the architecture upfront. I feel that one needs to experiment a lot (and fail a bit) before getting this part right.
  • ris 7y ago
    A good ORM acknowledges this and allows that to happen gracefully, while still allowing the 90%+ of straightforward queries to use the less error prone higher abstractions of the ORM.