We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am trying to migrate and connect to a PostgreSQL database using connection pooling, but I am getting the following error:
2024-01-08T12:15:12.889 [info] 2024-01-08T12:15:12.889135Z INFO sqlx::postgres::notice: relation "migrations" already exists, skipping 2024-01-08T12:15:13.030 [info] thread '<unnamed>' panicked at src/repo/postgres_migration.rs:70:14: 2024-01-08T12:15:13.030 [info] called `Result::unwrap()` on an `Err` value: Database(PgDatabaseError { severity: Error, code: "42P05", message: "prepared statement \"sqlx_s_1\" already exists", detail: None, hint: None, position: None, where: None, schema: None, table: None, column: None, data_type: None, constraint: None, file: Some("prepare.c"), line: Some(412), routine: Some("StorePreparedStatement") }) 2024-01-08T12:15:13.030 [info] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace 2024-01-08T12:15:13.035 [info] thread 'main' panicked at src/main.rs:108:19: 2024-01-08T12:15:13.035 [info] called `Result::unwrap()` on an `Err` value: Any { .. } 2024-01-08T12:15:13.344 [info] INFO Main child exited normally with code: 101
I found relevant information about the upstream here, and it seems that it have been stuck here for a long time: launchbadge/sqlx#67
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I am trying to migrate and connect to a PostgreSQL database using connection pooling, but I am getting the following error:
I found relevant information about the upstream here, and it seems that it have been stuck here for a long time: launchbadge/sqlx#67
The text was updated successfully, but these errors were encountered: