What can we do if the `primsa migrate dev` failed?...
# prisma-migrate
h
What can we do if the
primsa migrate dev
failed?
Copy code
Error: The migration 20210111021729_item_style_none failed when applied to the shadow database.
Fix the migration script and run yarn prisma migrate dev --preview-feature again.

P3006
Migration `20210111021729_item_style_none` failed to apply cleanly to a temporary database. 
Error:
Database error: Error accessing result set, column not found: itemStyle
   0: sql_migration_connector::flavour::postgres::sql_schema_from_migration_history
             at migration-engine/connectors/sql-migration-connector/src/flavour/postgres.rs:174
   1: sql_migration_connector::sql_database_migration_inferrer::validate_migrations
             at migration-engine/connectors/sql-migration-connector/src/sql_database_migration_inferrer.rs:89
   2: migration_core::api::DiagnoseMigrationHistory
             at migration-engine/core/src/api.rs:148
error Command failed with exit code 1.
info Visit <https://yarnpkg.com/en/docs/cli/run> for documentation about this command.
What I did is just add below
none
field in enum type.
Copy code
enum ItemStyle {
  none
  basic
  street
  ...
}
j
Hi @Hyo Could you create an issue here https://github.com/prisma/prisma/issues/new?assignees=&amp;labels=&amp;template=bug_report.md&amp;title= And provide the generated SQL from the migration.sql file with the before & after schema.prisma?
👌 1
h
Ok! I’ll do it when it is reproducible
💯 2
However, I was wondering, what would be the workaround if I face that error. What steps may I do without having to reset migration?
j
@Hyo So I’m curious why reset is not an option for your local dev workflow? Could it be solved with a seed script that you run after the reset to get data in the database?