HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
prisma
orm
TypeScript2018–2026
prisma / orm

orm

The Prisma ORM: write your application in TypeScript with human-readable queries instead of SQL. Host your database on Prisma Postgres and your app on Prisma Compute.

49Distinct people
74Mentions
1Explicit recommenders
47.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The Prisma ORM: write your application in TypeScript with human-readable queries instead of SQL. Host your database on Prisma Postgres and your app on Prisma Compute.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I love Prisma and am a huge fan of Nexus[1] in particular. But it's interesting that you mention transactions as Prisma does not yet support long running transactions[2]. I…

string used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:01:57 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year74 dated mentions

Observed mentions: 2018-12-03 19:57:14 UTC to 2026-09-16 17:43:54 UTC.

0510152018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 16 mentions; 1 submissions, 15 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 11 mentions; 1 submissions, 10 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 14 mentions; 2 submissions, 12 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC606
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC16115
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC10010
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC11110
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC14212
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC505
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC826
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC202

What Hacker News says

14 sources
I think maybe with Django, you could use a QuerySet with an F expression to do this? [0] Agreed that it's trivial in pure SQL. As a counter though, having worked at places using an ORM (mostly Django), and also where everything was raw SQL, the latter winds up having WILDLY inefficient schema and queries that the DB team (me) has to fix later. I lost any respect for Prisma when I learned it doesn't do JOINs in the DB. [1] [0]: https://docs.djangoproject.com/en/5.0/ref/models/expressions... [1]: https://github.com/prisma/prisma/issues/5184
In PostgreSQL internals: Things to know about update statements
nbrad·Dec 18, 2023Submission

Any Python ORMs worthy of production?

I’m hoping for something battle-tested that supports async/await and migrations. If your answer is some variation of “real programmers don’t use ORMs”... fair enough, I suppose. But here are the options as I see them: - Django: very mature ORM, migration support is great. But it doesn’t support async/await (https://docs.djangoproject.com/en/5.0/topics/async/), and these days FastAPI seems like a better option. FastAPI just needs an ORM, so => - SQLModel: from @tiangolo who created FastAPI, clean and good Pydantic support, so this would be my default option, but even though it seems to support async/await the doc page is blank (https://sqlmodel.tiangolo.com/advanced/), and for migrations you resort to the underlying => - SQLAlchemy: seems by far the largest/best supported, has async/await, has migrations through Alembic (it seems not as fu
Read the rest
lly-featured as Django’s?), but trying to use it has felt very kludgy/painful/verbose. - Tortoise: the README claims to fulfill my dreams, but I haven’t met anyone yet using it in prod? Anyone have experience they can share? - Any others I missed? Meanwhile in the JS/TS ecosystem, Prisma just added preview support for JOINs 2 weeks ago (https://github.com/prisma/prisma/releases/tag/5.7.0 !?!) and yet it seems ubiquitous (though I hear everyone’s moving to Drizzle). Advice greatly appreciated
2 points · Open discussion
jonjlee·Jun 11, 2023Submission

Ask HN: Is SQLAlchemy the industry standard Python ORM in 2023?

I'm starting a greenfield side project. I've only used Python in smaller projects without reason to hook up an ORM tool. In searching for choices now, the de facto standard seems to be SQLAlchemy, but I also see a number of references to Prisma[0][1] and other projects that claim to be a better, modern choice. What is the right choice for a brand new project at this time? [0] https://github.com/prisma/prisma [1] https://eash98.medium.com/why-sqlalchemy-should-no-longer-be-your-orm-of-choice-fo…
4 points · Open discussion
How do people on HN like Row Level Security? Is it a better way to handle multi-tenant in a cloud SaaS app vs `WHERE` clauses in SQL? Worse? Nicer in theory but less maintainable in practice? fwiw, Prisma has a guide on how to do RLS with it's client. While the original issue[0] remains open they have example code[1] with the client using client extensions[2]. I was going to try it out and see how it felt. [0]: https://github.com/prisma/prisma/issues/12735 [1]: https://github.com/prisma/prisma-client-extensions/blob/main... [2]: https://www.prisma.io/docs/concepts/components/prisma-client...
In Migrating from Supabase
I explained the other day to a friend how Prisma looks great but it's very unresponsive on Github [1], specially surprising since they raised a lot of money so I thought they'd have more resources. So he introduced me to the concept of FOSS-washing (in relation to greenwashing). Launch a cool open source piece of software, get big clients and funding thanks to it and then basically ignore Github or just dedicate enough resources to it so that it doesn't seem "dead". I had seen and complained about this before here in HN, how when Github said they were sunsetting Atom for lack of engagement I pointed out that the lack of engagement was... by them, not a single commit in few years so of course there was no activity [2] Edit: looking at the Github tracker now, it seems that now they use Github as the main tracking software? So there's a bunc
Read the rest
h of new issues by internal contributors with "bad description" (meaning it's probably the tip of the iceberg of an internal issue just for tracking, not the typical issue someone finds and reports), but the old ones sit there unanswered. [1] https://github.com/prisma/prisma/issues/4433 [2] https://news.ycombinator.com/item?id=31670443
In Prisma laying off 28% staff
I really like Prisma, and talk about it to anyone who'll listen, but it is still very new and as such I think doesn't have a lot of features figured out yet and some really surprising things do come up. One I discovered just the other day [0] was that if you pass an undefined value into a field in a where clause of findFirst, it's treated the same as if you didn't pass anything at all. If you do this with an id, for example, this can result in just the first record in the table being returned, because it's as though you have no where clause at all. Naturally this can lead to some surprising bugs if undefined values crop up at runtime, even potentially some really bad security bugs (imagine if this happens on the account table for instance). I don't mean this as a criticism, I think it is just a normal part of being new and exciting softwa
Read the rest
re, maturing over time. But it's always a tradeoff to be aware of. [0] https://github.com/prisma/prisma/issues/5149#issuecomment-13...
In I Migrated from a Postgres Cluster to Distributed SQLite with LiteFS

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.