This repository has been archived by the owner on Feb 8, 2018. It is now read-only.
Move is_locked from elsewhere to participants
#3012
Merged
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
| FROM elsewhere e | ||
| WHERE e.participant = p.username | ||
| AND e.is_locked; | ||
|
|
There was a problem hiding this comment.
Don't we want to remove the is_locked column from elsewhere?
There was a problem hiding this comment.
Of course, I just didn't put it in the branch.sql because dropping columns means I have to recreate my dev DB when I switch to another branch.
|
LGTM, merging. |
rohitpaulk
added a commit
that referenced
this pull request
Dec 14, 2014
Move `is_locked` from `elsewhere` to `participants`
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.
I guess this is a part of #1549 even though it's never been mentioned there.