Skip to content

prisma migrate --create-only needs an additional command to allow it to apply created migrations without supplying a name #1192

@jasonlewicki

Description

@jasonlewicki
{
  "$schema": "https://json-schema.org/schema",
  "version": 2,
  "title": "Prisma migrate dev executor",
  "description": "The migrate dev command updates your database using migrations during development and creates the database if it does not exist.",
  "type": "object",
  "properties": {
    "schema": {
      "type": "string",
      "description": "Specifies the path to the desired schema.prisma file to be processed instead of the default path. Both absolute and relative paths are supported."
    },
    "name": {
      "type": "string",
      "description": "The name of the migration."
    },
    "create-only": {
      "type": "boolean",
      "description": "Creates a new migration based on the changes in the schema but does not apply that migration."
    },
    "skip-seed": {
      "type": "boolean",
      "description": "Skip triggering seed."
    },
    "skip-generate": {
      "type": "boolean",
      "description": "Skip triggering generators (for example, Prisma Client)."
    }
  },
  "required": ["name"]
}

requires a name, and does not support deploying in dev --create-only migrations

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions