Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix broken link #5422

Merged
merged 1 commit into from
Nov 3, 2023
Merged

fix broken link #5422

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/300-guides/050-database/890-neon.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ Many aspects of using Prisma with Neon are just like using Prisma with any other
- model your database with the [Prisma Schema Language](/concepts/components/prisma-schema)
- use Prisma's [`postgresql` database connector](/concepts/database-connectors/postgresql) in your schema, along with the [connection string Neon provides you](https://neon.tech/docs/connect/connect-from-any-app)
- use [Introspection](/concepts/components/introspection) for existing projects if you already have a database schema on Neon
- use [`prisma migrate dev`](/concepts/components/prisma-migrate/migrate-development-productoin) to track schema migrations in your Neon database
- use [`prisma migrate dev`](/concepts/components/prisma-migrate/migrate-development-production) to track schema migrations in your Neon database
- use [`prisma db push`](/concepts/components/prisma-migrate/db-push) to push changes in your schema to Neon
- use [Prisma Client](/concepts/components/prisma-client) in your application to communicate with the database hosted by Neon

Expand Down
Loading