[Tadpole9181]

It's pretty obvious when somebody has only heard of Prisma, but never used it.

- Using `JOIN`s (with correlated subqueries and JSON) has been around for a while now via a `relationLoadStrategy` setting.

- Prisma has a Rust service that does query execution & result aggregation, but this is automatically managed behind the scenes. All you do is run `npx prisma generate` and then run your application.

- They are in the process of removing the Rust layer.

The JOIN setting and the removing of the middleware service are going to be defaults soon, they're just in preview.

[compton93]

They've been saying that for 3 years. We actually had a discount for being an early adopter. But hey its obvious Ive never used it and only heard of it.

[Tadpole9181]

The JOIN mode has been in preview for over a year and is slated for GA release within a few months. Which has been on their roadmap.

The removal of the rust service is available in preview for Postgres as of 6.7.[1]

Rewriting significant parts of a complex codebase used by millions is hard, and pushing it to defaults requires prolonged testing periods when the worst case is "major data corruption".

[1]: https://www.prisma.io/blog/try-the-new-rust-free-version-of-...

[compton93]

They've had flags and work arounds for ages. Not sure what point you are trying to make? But like you said I've never used it, only heard of it lol.

[paulddraper]

It is hard.

Harder than just doing joins.

[williamdclt]

Honestly, everything you say makes me want to stay far from prisma _more_.

All this complexity, additional abstractions and indirections, with all the bugs gootguns and gotchas that come with it... when I could just type "JOIN" instead.

[Tadpole9181]

Okay? It's one setting that will be the default in 2 months. And you could always write type-safe SQL manually instead.

i greatly envy y'all having projects where the biggest complexity is... A single setting once, that's clearly documented. We live in very different worlds, apparently.