News for hackers. Stuff that matters.
Re:How We Turn Authorization Logic into SQL by throw_m239339 on Tuesday November 23, 2021 @02:51PM (#29322457)
Well (most) ORM often cannot take advantage of CTE, group concat, array types, json types and what not when building queries from code, for obvious reason. So they often can't return multi-dimensional data in a single query.

But ORM are still useful to get an application off the ground fast.

Re:How We Turn Authorization Logic into SQL by gfody on Tuesday November 23, 2021 @03:13PM (#29322761)
do ORMs still target lowest common denominator ansi sql? I only know that EF doesn't - it has "providers" for each rdbms it supports and will liberally emit CTEs and db specific language features like "outer apply" or "join lateral" but then stupidly ignore powerful features like "for json" or "json_agg/json_build_object" which could eliminate the outrageously naive way it encodes 1:m and m:m results - it boggles how smart and stupid orms are at the same time.
Re:How We Turn Authorization Logic into SQL by jiggawatts on Tuesday November 23, 2021 @04:28PM (#29323794)
JSON is too “lossy” to use automatically.
Re:How We Turn Authorization Logic into SQL by aidos on Tuesday November 23, 2021 @04:06PM (#29323538)
To be clear, sqlalchemy does support those features.