Modern RDBMSes can handle most of the ORM use cases at their end. What's wrong with VIEWs, for instance? Plus it solves the whole schema impedance mismatch thi

Modern RDBMSes can handle most of the ORM use cases at their end. What's wrong with VIEWs, for instance? Plus it solves the whole schema impedance mismatch thing to just leave it up to the DB. ORMs aren't that great. Having spent the past five years primarily with an object database that is also fully SQL (ISC Caché) I find myself preferring SQL more and more. Even when you have the ORM within the bloody database I'm going SQL. The string thing isn't an SQL problem, it's a tooling one. The only tool per se should be pgAdmin or an equivalent. And in your application the only "SQL" that should be written is SELECT * FROM viewforthisfunctionality and select runupsertwithjsonobjectthatpgorplpgsqlcanreadjus tfine(json)