search

prisma / migrate

Issues for Prisma Migrate are now tracked at prisma/prisma. This repo was used to track issues for Prisma Migrate Experimental and is now deprecated.
https://www.prisma.io/docs/concepts/components/prisma-migrate
Apache License 2.0
767 stars 22 forks source link

migrate up fail #669

Closed devdany closed 3 years ago

devdany commented 3 years ago

Hi Prisma Team! Prisma Migrate just crashed.

Versions

Name Version
Platform darwin
Node v14.11.0
Prisma CLI 2.11.0
Binary 58369335532e47bdcec77a2f1e7c1fb83a463918

Error

Error: Error in migration engine.
Reason: [migration-engine/connectors/sql-migration-connector/src/sql_migration_persistence.rs:91:66] called `Result::unwrap()` on an `Err` value: ConnectionError { quaint_error: Error { kind: QueryError(Server(ServerError { code: 1366, message: "Incorrect string value: \'\\xEC\\xA7\\x80\\xEA\\xB8\\x88...\' for column `smartclinic-staging`.`_Migration`.`datamodel` at row 1", state: "22007" })), original_code: Some("1366"), original_message: Some("Incorrect string value: \'\\xEC\\xA7\\x80\\xEA\\xB8\\x88...\' for column `smartclinic-staging`.`_Migration`.`datamodel` at row 1") }, connection_info: Mysql(MysqlUrl { url: Url { scheme: "mysql", host: Some(Domain("smartclinic-development.ccquqcy2bny4.ap-northeast-2.rds.amazonaws.com")), port: Some(3306), path: "/smartclinic-staging", query: None, fragment: None }, query_params: MysqlUrlQueryParams { ssl_opts: SslOpts { pkcs12_path: None, password: None, root_cert_path: None, skip_domain_validation: false, accept_invalid_certs: false }, connection_limit: None, use_ssl: false, socket: None, socket_timeout: None, connect_timeout: None } }) }

Please create an issue in the migrate repo with
your `schema.prisma` and the prisma command you tried to use 🙏:
https://github.com/prisma/migrate/issues/new
tomhoule commented 3 years ago

Thanks for taking the time to report this issue!

We've recently released a Prisma Migrate Preview (2.1.3.0 release notes), which has quite a few changes compared to the previous experimental version. We believe this issue is no longer relevant in this new version, so we are closing this.

We would encourage you to try out Prisma Migrate Preview. If you come across this or any other issue in the preview version, please feel free to open a new issue in prisma/prisma. For general feedback on Prisma Migrate Preview, feel free to chime in on this issue.