This repository has been archived by the owner on Mar 2, 2019. It is now read-only.
Guide user to the correct method call in DROP statement #21
Conversation
This file contains 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
alexfu#20 Users could select the wrong method when building a DROP statement. * Change the return type of ifExists to SegmentBuilder.
alexfu
added a commit
that referenced
this pull request
Jul 4, 2015
Guide user to the correct method call in DROP statement
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
@alexfu, please review the request. Thanks to @monxalo for the idea.
In relation to #20, this will guide user to the correct method in DROP statement.
Users could select the wrong method when building a DROP statement.
ifExists()toSegmentBuilder.