[jmknoll]

Completely off-topic, but do you like prisma, and how are you using it (scale, complexity, solo vs team, etc).

I toyed around with it a while back, and it looked potentially awesome, but different enough that I was worried about using it on a work project in case it failed in some use case.

Im so sick of the SQL ORM situation in Typescript, but Prisma might have an answer.

[panzi]

Prisma has this one glaring issue: https://github.com/prisma/prisma/issues/10649

Segmentation fault with NodeJS 18. Its about prisma having linked a different version of OpenSSL than NodeJS. A workaround is to use the "binary" engine, meaning you run another process, talk via IPC to that, and that then talks to the DB, which is ridiculously roundabout.

But this issue is finally worked on, so once that is fixed its good.

[bottlepalm]

It's good, but verbose, you can't select nested objects by just doing lesson.mapped.sections.course .. etc.. you have have to do something like

    lesson: {
        select: {
            id: true,
            slug: true,
            title: true,
            mapped_sections: {
                select: {
                    id: true,
                    slug: true,
                    section: {
                        select: {
                            id: true,
                            title: true,
                            course: {
                                select: {
                                    id: true,
                                    slug: true,
                                    title: true

[olalonde]

It's a solo project, CRUD stuff, but having used pretty much all JavaScript/TypeScript ORMs in existence, I can say that Prisma is way ahead of the competition. I would personally recommend it. A traditionally cumbersome and annoying thing about trying a new ORM is that you basically have to re-learn a pseudolanguage for building SQL queries but that hasn't been an issue this time, thanks to ChatGPT. So overall, happy with Prisma and plan to keep using it.