-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
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
MySQL issue 42000 #326
Comments
BruH MySql always be disappointing. I will probably drop support for it next major release. Will it be possible for you to switch to Postgres? |
I can switch to postgres, however all my currently hosted projects use mariadb and I would like to keep the containers to a minimum. If you like I can def look into switching to postgres. |
I would definitely suggest you do. I won't be able to fix this anyway without #294 (comment) being resolved. |
Blocked by SeaQL/sea-orm#1839 |
Quick question, would this affect SQLite aswell? and what are the downsides of using SQlite, I've heard a lot of bad things about it lol. |
I haven't really used Sqlite all that much. During development mode I noticed sqlite allows you to create foreign kys to tables that do not exist. |
I'm trying to setup ryot using mysql and getting this error:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Exec(SqlxError(Database(MySqlDatabaseError { code: Some("42000"), number: 1059, message: "Identifier name 'fk_partial-metadata-to-metadata-group_id-metadata-partial-metadata_id' is too long" })))', apps/backend/src/main.rs:137:35 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
any ideas?
The text was updated successfully, but these errors were encountered: