Prisma
prisma.io › home › pull › pull › pull
prisma db pull | Introspect Database to Prisma Schema | Prisma Documentation
Sync your Prisma schema from an existing database with prisma db pull. Introspect tables, relations, and generate Prisma models automatically.
Fig
fig.io › manual › prisma › db › pull
prisma db pull | Fig
prisma db pull · prisma db push · prisma db seed · prisma db execute · prisma version · prisma version · prisma version --json · No description · On this page ·
Is Prisma DB Pull reliable?
Hey there, Nikolas from Prisma here! If I continue to build my DB architecture directly in the db, is the Prisma db pull a reliable method to keep my Prisma schema up to date and accurate so I can get the typing's? This is definitely a valid approach! I think a lot of people prefer writing their own migrations (using whatever tool they prefer for that) and then use Prisma's introspection to update their Prisma schema — the main thing to be aware of with that workflow is that you need to run npx prisma generate after each introspection run to make sure the generated Prisma Client types and API get updated. This is also covered in the docs as a typical Prisma workflow: SQL migrations and introspection More on reddit.com
Add `prisma db pull` command for introspection
Add prisma db pull command for introspection, with the same behavior Document prisma db pull in CLI help output Should prisma db pull be added in Preview? If not, we should change the help output t... More on github.com
Warning: Think twice before using Prisma in large projects
Hey there, I'm Nikolas from the Prisma team. Thanks a lot for raising these issues, we're always looking to improve so we very much appreciate feedback like this! It sounds like your main issue revolves around the size of the generated index.d.ts file, right? (Since the TS server crashing and the worsened DX are consquences of that)? Thank you as well for already pointing to the open issue for this! I understand that it must be super frustrating to have your editor become slow and autocomplete stop working because of that (and honestly, having an issue open for 4,5 yars sounds equally frustrating to me). I will raise the urgency of this to our Engineering team and hope that we'll get to this soon. We actually recently changed our approach to OSS governance and made it more transparent, exactly because of issues like that one that have been around for so long. In the meantime, could I ask you to add a comment to the issue? Ideally, you can also share your schema (maybe in a GitHub Gist ?) so that our engineers can reproduce it? Regarding JOINs, we released native DB-level joins that are using a mix of LATERAL joins and JSON aggregation about one year ago, so hopefully there shouldn't be any issues around that any more. If you do end up seeing slow queries, please open an issue ! We've invested a lot into performance in the last 1-2 years and are eager to fix any slow query we become aware of. Thanks again for sharing this and please let me know if I can help in any other way! More on reddit.com
stuck with prisma and supabase database update
Oh i did this Connect to Supabase via connection pooling with Supavisor. DATABASE_URL="postgres://postgres.[your-supabase-project]:[password]@aws-0-[aws-region].pooler.supabase.com:6543/postgres?pgbouncer=true" Direct connection to the database. Used for migrations. DIRECT_URL="postgres://postgres.[your-supabase-project]:[password]@aws-0-[aws-region].pooler.supabase.com:5432/postgres" datasource db { provider = "postgresql" url = env("DATABASE_URL") directUrl = env("DIRECT_URL") } But still stuck More on reddit.com
YouTube
youtube.com › prisma
Using the Prisma DB Pull Command - YouTube
Prisma 2.18 introduced a change to the way databases are introspected.Instead of using the `prisma introspect` command, developers should now use the `prisma...
Published March 3, 2021 Views 3K
MCP Servers
mcpservers.org › home › agent skills library › prisma-cli-db-pull
prisma-cli-db-pull | Agent Skills Library
Complete reference for Prisma CLI commands, options, and workflows across setup, migrations, and database operations. Covers 20+ commands organized by priority: setup ( init ), generation ( generate ), development ( dev ), database operations ( db pull/push/seed/execute ), and migrations ( migrate dev/deploy/reset/status/diff/resolve ) Includes Prisma 7.x changes: new prisma.config.ts configuration file, removed flags ( --skip-generate , --skip-seed , --schema , --url ), and explicit...
Author prisma
Reddit
reddit.com › r/webdev › how to go from database design to prisma schema and api development .
r/webdev on Reddit: How to go from database design to Prisma Schema and API Development .
January 10, 2026 - This approach lets you design your database visually, tweak it the way you want, deploy it easily, and then pull the schema using prisma db pull to generate a schema.prisma file. From there, you can start writing your API endpoints in no time. you can watch the full tutorial here : https://youtu.be/gnXH2GgmD8A
Reddit
reddit.com › r/node › is prisma db pull reliable?
r/node on Reddit: Is Prisma DB Pull reliable?
August 14, 2023 -
My backend is a fastify/Prisma to a PostgreSQL DB, I am much more comfortable with building my DB tables and constraints (PK, FK, etc) via SQL rather than Prisma's relationships schema.
My question is: If I continue to build my DB architecture directly in the db, is the Prisma db pull a reliable method to keep my Prisma schema up to date and accurate so I can get the typing's?
I just am able to comprehend and explain the relationship much better via SQL rather than via the model references.
Top answer 1 of 3
8
Why then use Prisma at all? Just use any query builder if you like pure SQL. The other issue is that now you also need to handle the migrations by yourself. Maybe you should consider an ORM like TypeORM?
2 of 3
4
Hey there, Nikolas from Prisma here! If I continue to build my DB architecture directly in the db, is the Prisma db pull a reliable method to keep my Prisma schema up to date and accurate so I can get the typing's? This is definitely a valid approach! I think a lot of people prefer writing their own migrations (using whatever tool they prefer for that) and then use Prisma's introspection to update their Prisma schema — the main thing to be aware of with that workflow is that you need to run npx prisma generate after each introspection run to make sure the generated Prisma Client types and API get updated. This is also covered in the docs as a typical Prisma workflow: SQL migrations and introspection
GitHub
github.com › prisma › prisma › issues › 5836
Add `prisma db pull` command for introspection · Issue #5836 · prisma/prisma
February 25, 2021 - Flag --preview-feature Run preview Prisma commands Usage $ prisma db [command] [options] --preview-feature Options -h, --help Display this help message --schema Custom path to your Prisma schema Commands push Push the state from Prisma schema to the database during prototyping (preview) pull Pull the state from the database to the Prisma schema using introspection seed Seed your database (preview) Examples Using prisma db push $ prisma db push --preview-feature Using prisma db seed $ prisma db seed --preview-feature
Author prisma
GitHub
github.com › prisma › prisma › discussions › 15775
How can i pull or introspect a defined list tables · prisma/prisma · Discussion #15775
Hi @kaykhan 👋 It's not possible at the moment, npx prisma db pull will introspect all the database tables.
Author prisma
DEV Community
dev.to › digitaldrreamer › prisma-db-push-or-pull-stuck-1g4j
Prisma db push or pull stuck? - DEV Community
January 7, 2026 - For example, running npx prisma db push took 9 minutes here and still failed: To resolve this, I needed to switch to a direct connection string using port 5432 instead. I tried changing it on the Supabase dashboard and then saw this: ... # Old Pooled Connection DATABASE_URL="postgresql://...@db.supabase.co:6543/db" DIRECT_URL="postgresql://...@db.supabase.co:6543/db" # New Direct Connection DATABASE_URL="postgresql://...@db.supabase.co:6543/db" DIRECT_URL="postgresql://...@db.supabase.co:5432/db"