0Pricing
Next.js 15 Fullstack (App Router + Server Actions) · Pelajaran

Migrasi Skema Basis Data

Kelola perubahan pada skema basis data menggunakan Prisma Migrate untuk pengembangan dan penerapan yang lancar.

Migrasi Skema Basis Data adalah pelajaran Next.js 15 Fullstack (App Router + Server Actions) gratis di CoddyKit. Ini adalah pelajaran 3 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Next.js 15 Fullstack (App Router + Server Actions), dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Next.js 15 Fullstack (App Router + Server Actions) mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

What are Database Migrations?

As your application evolves, so does its database structure, also known as its schema.

Database migrations are like version control for your database schema. They are a way to manage changes to your database structure in a controlled and trackable manner.

  • They ensure your database matches your application's needs.
  • They prevent data loss during schema changes.
  • They provide a clear history of all schema modifications.

Why Use Prisma Migrate?

Managing database schema changes manually can be complex and error-prone. Prisma Migrate simplifies this process significantly.

  • Automatic Generation: It generates SQL migration files based on changes in your Prisma schema.
  • History Tracking: It keeps a history of applied migrations, making rollbacks and team collaboration easier.
  • Environment Consistency: Ensures your development, staging, and production databases all have the correct schema.

Your Prisma Schema File

Prisma Migrate uses your schema.prisma file as the source of truth for your database schema. Any changes you want to make to your database structure start here.

Let's recall a basic schema.prisma setup:

generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model User {
  id    Int     @id @default(autoincrement())
  name  String
  posts Post[]
}

model Post {
  id        Int      @id @default(autoincrement())
  title     String
  content   String?
  published Boolean  @default(false)
  author    User     @relation(fields: [authorId], references: [id])
  authorId  Int
}

Initializing Your First Migration

When you first set up your Prisma schema, you'll want to create an initial migration to apply this schema to your database. You use the prisma migrate dev command for this.

This command does two main things:

  1. Generates a new migration file (SQL) in the prisma/migrations folder.
  2. Applies the migration to your database.
npx prisma migrate dev --name initial_setup

Understanding Migration Files

After running npx prisma migrate dev, Prisma creates a new folder inside prisma/migrations with a timestamp and the name you provided (e.g., 20231026123456_initial_setup).

Inside this folder, you'll find:

  • migration.sql: This file contains the raw SQL commands generated by Prisma to create or alter your database tables.
  • migration.js or migration.ts: (If using TypeScript/JavaScript) Metadata about the migration.

It's important to commit these files to your version control system!

Making Schema Changes

Now, let's say you want to add an email field to your User model. You simply update your schema.prisma file.

Prisma will detect this change and help you generate a new migration.

model User {
  id    Int     @id @default(autoincrement())
  name  String
  email String  @unique // Added new field
  posts Post[]
}

Generating a New Migration

After modifying your schema.prisma, run npx prisma migrate dev again. Prisma will compare your updated schema with the current database state and generate a new migration file.

It will then apply this new migration, adding the email column to your User table.

npx prisma migrate dev --name add_user_email

Applying Migrations in Production

For production environments, you typically use npx prisma migrate deploy. This command applies all pending migrations that have not yet been run on the database.

Unlike migrate dev, deploy does not generate new migration files; it only applies existing ones. This makes it safe and predictable for production deployments.

npx prisma migrate deploy

Checking Migration Status

To see which migrations have been applied to your database and which are pending, you can use the npx prisma migrate status command.

This is useful for debugging or ensuring your database is up-to-date with your application's expected schema.

npx prisma migrate status

Prisma Migrate Commands Quiz

Which of the following statements correctly describe the purpose of Prisma Migrate commands?

Recap: Schema Migrations

Great job! You've learned how to manage your database schema effectively using Prisma Migrate.

  • Prisma Migrate helps version control your database schema.
  • You define schema changes in schema.prisma.
  • npx prisma migrate dev creates and applies migrations in development.
  • npx prisma migrate deploy applies existing migrations in production.
  • npx prisma migrate status checks the current migration state.

This powerful tool ensures your database structure stays consistent and aligned with your application's needs as it grows.

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Migrasi Skema Basis Data” gratis?

Ya — teks lengkap “Migrasi Skema Basis Data” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Next.js 15 Fullstack (App Router + Server Actions), upgrade ke CoddyKit PRO. Kursus Next.js 15 Fullstack (App Router + Server Actions) mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Migrasi Skema Basis Data”?

Kelola perubahan pada skema basis data menggunakan Prisma Migrate untuk pengembangan dan penerapan yang lancar. Kamu berlatih Next.js 15 Fullstack (App Router + Server Actions) dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai Next.js 15 Fullstack (App Router + Server Actions)?

Tidak diperlukan pengalaman sebelumnya. Next.js 15 Fullstack (App Router + Server Actions) di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 3 dari 4.

Berapa lama pelajaran “Migrasi Skema Basis Data” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran Next.js 15 Fullstack (App Router + Server Actions) ini?

Ya. Setiap pelajaran Next.js 15 Fullstack (App Router + Server Actions) menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

  1. Menyiapkan Prisma ORM
  2. CRUD dengan Server Actions
  3. Migrasi Skema Basis Data
  4. Pengisian Awal Basis Data dan Pengumpulan Koneksi
← Kembali ke Next.js 15 Fullstack (App Router + Server Actions)