3 ms·

I sort of agree here. I tend to stay away from ORMs in general, but I'd probably use one if it actually justified itself. Most ORMs I've used basically just abs

I sort of agree here. I tend to stay away from ORMs in general, but I'd probably use one if it actually justified itself. Most ORMs I've used basically just abstract the data layer so you don't have to write own SQL, but that in itself comes at a cost (and almost all of them are bound to eventually write some really crappy SQL for you and cause performance bottlenecks). If there's not an appreciable benefit besides just not having to write as much SQL, then it's not really worth using.

lemontruth 6y ago
In one way or other you cannot avoid the SQL builder, this ORM is building it in the user's code base. I believe in ballance, you need the query builder for simple queries (that makes most of your queries) but the complex queries should be also supported (even if they are not portable) We have written exactly this kind of ORM https://github.com/holdfenytolvaj/pogi https://github.com/holdfenytolvaj/pogi It saves you a lot of code writing, but is not taking away the power of postgresql (however it is anchored to postgresql)