Now only "<numbers>/<numbers>" can exist in the ba_page field #55
Conversation
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
…cate beer Not tested!
Was tested with a few sample ba_page's
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Was tested with a few sample ba_page's
I made this pull request so that when checking for a duplicate beer the site has a better time finding one if it exists.
Will likely need to run the following UPDATE MySQL query to get everything back in line (I've already ran this, so this is just in case someone else adds a beer between now and when you get to this pull request):
UPDATE beers SET ba_page=SUBSTRING_INDEX(ba_page,"/",2) WHERE ba_page REGEXP '^[0-9]+/[0-9]+/.*$'