-
Notifications
You must be signed in to change notification settings - Fork 690
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
Exposed tries to create the same foreign key constraint even if one already exists #843
Comments
Thank you for the report. Fixed in master and will be released soon in 0.23.1 |
Hi ! I experiment the same type of error with Exposed 0.25.1 when I use createMissingTablesAndColumns Example Tables :
Then the log :
This log repeat itself 3 or 4 times Any idea ? |
Same for me, issue still exists in 0.41.1 |
Still the issue persists on 0.45 |
Hi all,
Just updated exposed to 0.22.1 from 0.17.7 and am facing this issue. The following tables
player
andsession
haven't been changed since the update.When trying to call
SchemaUtils.createMissingTablesAndColumns
(which supposedly shouldn't have any affect since the tables haven't changed) – I'm getting the following errorFor some reason it attempts to create the same foreign key for the table session
fk_session_player_id_id
, which it already hasWhat would be the solution?
Thanks
The text was updated successfully, but these errors were encountered: