Wasp•2y ago•

8 replies

Issue with @default([]) in schema.prisma during migration from Wasp 13 to 14

I am currently migrating our production application from version 13 to 14, following the migration guide. I’ve made all the necessary code changes, but when I ran the final command, wasp db migrate-dev, I encountered the following error:

Wasp couldn't parse your schema.prisma file, please check if you have any errors in it.

Wasp couldn't parse your schema.prisma file, please check if you have any errors in it.

This was a puzzle to me because the same schema used to work when it was part of the main.wasp file. After some debugging, I ran the following prisma command to check if I would encounter the same error:

prisma validate --schema=./schema.prisma

prisma validate --schema=./schema.prisma

To my surprise, the prisma command passed and returned:

The schema at schema.prisma is valid 🚀

The schema at schema.prisma is valid 🚀

I then created a minimal reproducible example to isolate the problem and was able to replicate the issue. Here’s the

schema.prisma

schema.prisma

file that triggers the error:

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

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

// Use Prisma Schema file to define your entities: https://www.prisma.io/docs/concepts/components/prisma-schema
// Run `wasp db migrate-dev` in the CLI to create the database tables
// Then run `wasp db studio` to open Prisma Studio and view your db models
model User {
  id    Int    @id @default(autoincrement())
  tasks Task[]
}

model Task {
  id          Int     @id @default(autoincrement())
  description String
  isDone      Boolean @default(false)
  user        User    @relation(fields: [userId], references: [id])
  userId      Int
  someField          String[]       @default([])
}

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

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

// Use Prisma Schema file to define your entities: https://www.prisma.io/docs/concepts/components/prisma-schema
// Run `wasp db migrate-dev` in the CLI to create the database tables
// Then run `wasp db studio` to open Prisma Studio and view your db models
model User {
  id    Int    @id @default(autoincrement())
  tasks Task[]
}

model Task {
  id          Int     @id @default(autoincrement())
  description String
  isDone      Boolean @default(false)
  user        User    @relation(fields: [userId], references: [id])
  userId      Int
  someField          String[]       @default([])
}

The issue seems to be with the

someField String[] @default([])

someField String[] @default([])

line. Setting the default value to

@default([])

@default([])

is causing the command to fail, even though this syntax worked in earlier versions of Wasp.

If I remove

@default([])

@default([])

from the schema and rerun

wasp db migrate-dev

wasp db migrate-dev

, the migration proceeds without errors.

Can anyone offer some guidance or suggestions on how to address it?

Issue with @default([]) in schema.prisma during migration from Wasp 13 to 14

Wasp couldn't parse your schema.prisma file, please check if you have any errors in it.

Wasp couldn't parse your schema.prisma file, please check if you have any errors in it.

prisma validate --schema=./schema.prisma

prisma validate --schema=./schema.prisma

To my surprise, the prisma command passed and returned:

The schema at schema.prisma is valid 🚀

The schema at schema.prisma is valid 🚀

I then created a minimal reproducible example to isolate the problem and was able to replicate the issue. Here’s the

schema.prisma

schema.prisma

file that triggers the error:

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

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

// Use Prisma Schema file to define your entities: https://www.prisma.io/docs/concepts/components/prisma-schema
// Run `wasp db migrate-dev` in the CLI to create the database tables
// Then run `wasp db studio` to open Prisma Studio and view your db models
model User {
  id    Int    @id @default(autoincrement())
  tasks Task[]
}

model Task {
  id          Int     @id @default(autoincrement())
  description String
  isDone      Boolean @default(false)
  user        User    @relation(fields: [userId], references: [id])
  userId      Int
  someField          String[]       @default([])
}

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

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

// Use Prisma Schema file to define your entities: https://www.prisma.io/docs/concepts/components/prisma-schema
// Run `wasp db migrate-dev` in the CLI to create the database tables
// Then run `wasp db studio` to open Prisma Studio and view your db models
model User {
  id    Int    @id @default(autoincrement())
  tasks Task[]
}

model Task {
  id          Int     @id @default(autoincrement())
  description String
  isDone      Boolean @default(false)
  user        User    @relation(fields: [userId], references: [id])
  userId      Int
  someField          String[]       @default([])
}

The issue seems to be with the

someField String[] @default([])

someField String[] @default([])

line. Setting the default value to

@default([])

@default([])

is causing the command to fail, even though this syntax worked in earlier versions of Wasp.

If I remove

@default([])

@default([])

from the schema and rerun

wasp db migrate-dev

wasp db migrate-dev

, the migration proceeds without errors.

Can anyone offer some guidance or suggestions on how to address it?

Issue with @default([]) in schema.prisma during migration from Wasp 13 to 14

Issue with @default([]) in schema.prisma during migration from Wasp 13 to 14

Continue the conversation

Wasp

Similar Threads

Continue the conversation

Wasp

Similar Threads