Re:How We Turn Authorization Logic into SQL
by airstrike on Tuesday November 23, 2021 @04:15PM
(#29323642)
Building bad queries with an ORM isn't necessarily the ORM engine's fault. It's really just a tool and, as such, its value really relies on one's proficiency with it.
One simple but illustrative example: https://docs.djangoproject.com/en/3.2/ref/models/querysets/#...
Re:How We Turn Authorization Logic into SQL
by aidos on Tuesday November 23, 2021 @04:05PM
(#29323531)
But you can build any query with Sqlalchemy - even when using the ORM rather than the Core, you still have that control, right?
Don’t get me wrong, I’ve read stuff by these guys and I know they know what they’re talking about. Certainly, if you have to make it work for Django as well you’d be considering going straight to sql.
As and aside, I walked through their stuff a little while back and I’m very interested in what they’re building.
Re:How We Turn Authorization Logic into SQL
by gfody on Tuesday November 23, 2021 @02:24PM
(#29322099)
agree this seems like the worst of both worlds between doing things application-side and doing things database-side. imo you're much better off embracing your db's security features
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.
Live by ORM, die by ORM. This strikes me as particularly bad because these authorization queries may be running on every request. It's great to see Oso went direct to SQL to address this. And the asides about logical programming were fun as well.