Inconsistent table names in migrations

Bug description

The capitalization for generated table names appears to be inconsistent. When creating new tables, the migrations contain the capitalized and correct version of the table names, however altering the model causes an alter migration to be created with a fully lowercase version of the table name. This causes issues where migrate fails because it cannot find the right table.

Creation migration:

Alter migration:

This causes my production setup to break with The underlying table for model 'report' does not exist.

How to reproduce

1. Create a migration adding a new table
2. Create a migration that alters the previously created table
3. The generated alter query will use a lowercase version of the table name

Expected behavior

The migration files should contain the actual model names, which in my case are capitalized

Environment & setup

• OS: Windows 10
• Database: MariaDB
• Node.js version: v12.18.4
• Prisma version:

prisma               : 2.22.0
@prisma/client       : 2.22.0
Current platform     : windows
Query Engine         : query-engine 60cc71d884972ab4e897f0277c4b84383dddaf6c (at node_modules\@prisma\engines\query-engine-windows.exe)
Migration Engine     : migration-engine-cli 60cc71d884972ab4e897f0277c4b84383dddaf6c (at  node_modules\@prisma\engines\migration-engine-windows.exe)
Introspection Engine : introspection-core 60cc71d884972ab4e897f0277c4b84383dddaf6c (at node_modules\@prisma\engines\introspection-engine-windows.exe)
Format Binary        : prisma-fmt 60cc71d884972ab4e897f0277c4b84383dddaf6c (at node_modules\@prisma\engines\prisma-fmt-windows.exe)
Default Engines Hash : 60cc71d884972ab4e897f0277c4b84383dddaf6c
Studio               : 0.379.0
Preview Features     : orderByRelation

[macjuul]

I’ve managed to reproduce it with a simple example

Initial schema:

generator client {
    provider        = "prisma-client-js"
    previewFeatures = ["orderByRelation"]
}

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

model User {
    id   Int    @id @default(autoincrement())
    name String
}

Which generates the following migration:

-- CreateTable
CREATE TABLE `User` (
    `id` INTEGER NOT NULL AUTO_INCREMENT,
    `name` VARCHAR(191) NOT NULL,

    PRIMARY KEY (`id`)
) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

If I now add a new status field to my User model like so:

model User {
    id     Int    @id @default(autoincrement())
    name   String
    status String @default("active")
}

The following migration will be generated, this time with a lowercase table name:

-- AlterTable
ALTER TABLE `user` ADD COLUMN `status` VARCHAR(191) NOT NULL DEFAULT 'active';

[pantharshit00]

Closing in favour of https://github.com/prisma/prisma/issues/6972