BUG: Include drop for foreign keys without index when dropping table#3164
Merged
rob-bygrave merged 4 commits intoebean-orm:masterfrom Aug 17, 2023
Merged
Conversation
jonasPoehler
added a commit
to FOCONIS/ebean
that referenced
this pull request
Aug 16, 2023
…tatement when dropping their table
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
With this change, foreign keys without a
forgeignKeyIndexare included in the drop statements when dropping their corresponding table. This was an oversight in #2933