Up and Running with Prisma and PlanetScale
Lesson write-up coming soon
Up and Running with Prisma and PlanetScale
Prisma and PlanetScale
How to Handle Code Changes After Schema Updates
RyanChenkie
Full Stack Instructor
When we use Prisma with PlanetScale, we don't use Prisma's migrate feature. This means that we need to consider the ramifications of our app code being out of sync with our data model. In this lesson, we see how to use the expand and contract pattern to make this simpler to manage.
Prisma and PlanetScale
What is PlanetScale?
PlanetScale offers a unique way for developers to host and manage a MySQL-c...
Install the PlanetScale CLI
The PlanetScale CLI allows us to manage almost everything from the command ...
Create a PlanetScale Database
To get Prisma wired up to PlanetScale, we need to start by getting a databa...
Connect to a PlanetScale Database
PlanetScale provides a few different ways for us to connect to our database...
Create a Node and Prisma Backend
In this lesson, we create a simple Node.js app that uses Prisma and see how...
Create a Prisma Schema
To get some data in our PlanetScale database, we first need to start with a...
Create Test Data Using Faker
The best way to make sure our database is working properly is to add some d...
Update the Schema and Open a Deploy Request
The way we change our data schema is different when we use PlanetScale. We ...
How to Handle Code Changes After Schema Updates
When we use Prisma with PlanetScale, we don't use Prisma's migrate feature....
How to Handle Connection Strings
When we use connection strings that PlanetScale provides, we sometimes need...
Switch from SQLite to PlanetScale
In the Getting Started with Prisma course, we use a simple SQLite database....
Lesson Resources
Get the code for this lesson