zaloster Comments - Answer Overflow

zaloster

Posts Comments

PPrisma

•Created by zaloster on 1/31/2025 in #help-and-questions

read replicas extension

Thank you very much 🫶

9 replies

PPrisma

•Created by zaloster on 1/31/2025 in #help-and-questions

read replicas extension

In package.json it's still fixed to 5.2.0 and also you can check this issue: https://github.com/prisma/extension-read-replicas/issues/41 Seems like the extension it's abandoned

9 replies

PPrisma

•Created by zaloster on 11/5/2024 in #help-and-questions

Migrations taking too long

Thank you very much

13 replies

PPrisma

•Created by zaloster on 11/5/2024 in #help-and-questions

Migrations taking too long

Hi @Nurul , do you need any extra info that may help you? Thanks

13 replies

PPrisma

•Created by zaloster on 11/5/2024 in #help-and-questions

Migrations taking too long

DEBUG="prisma:migrate*" pnpm exec prisma migrate dev --skip-generate Using pnpm just in case it matters

13 replies

PPrisma

•Created by zaloster on 11/5/2024 in #help-and-questions

Migrations taking too long

Environment variables loaded from .env
Prisma schema loaded from prisma/schema
Datasource "db": MySQL database "database-wa" at "host.docker.internal:3306"

prisma:migrate:dev {
  "devDiagnostic": "{\n  \"action\": {\n    \"tag\": \"reset\",\n    \"reason\": \"Drift detected: Your database schema is not in sync with your migration history.\\n\\nThe following is a summary of the differences between the expected database schema given your migrations files, and the actual schema of the database.\\n\\nIt should be understood as the set of changes to get from the expected schema to the actual schema.\\n\\n[+] Added tables\\n  - flyway_schema_history\\n\"\n  }\n}"
} +418385ms
Drift detected: Your database schema is not in sync with your migration history.

The following is a summary of the differences between the expected database schema given your migrations files, and the actual schema of the database.

It should be understood as the set of changes to get from the expected schema to the actual schema.

[+] Added tables
  - flyway_schema_history

? We need to reset the MySQL database "database-wa" at "host.docker.internal:3306"
Do you want to continue? All data will be lost. › (y/N)

Environment variables loaded from .env
Prisma schema loaded from prisma/schema
Datasource "db": MySQL database "database-wa" at "host.docker.internal:3306"

prisma:migrate:dev {
  "devDiagnostic": "{\n  \"action\": {\n    \"tag\": \"reset\",\n    \"reason\": \"Drift detected: Your database schema is not in sync with your migration history.\\n\\nThe following is a summary of the differences between the expected database schema given your migrations files, and the actual schema of the database.\\n\\nIt should be understood as the set of changes to get from the expected schema to the actual schema.\\n\\n[+] Added tables\\n  - flyway_schema_history\\n\"\n  }\n}"
} +418385ms
Drift detected: Your database schema is not in sync with your migration history.

The following is a summary of the differences between the expected database schema given your migrations files, and the actual schema of the database.

It should be understood as the set of changes to get from the expected schema to the actual schema.

[+] Added tables
  - flyway_schema_history

? We need to reset the MySQL database "database-wa" at "host.docker.internal:3306"
Do you want to continue? All data will be lost. › (y/N)