Fix ORM Create FullText index error if no text colums founded#1950
Merged
Conversation
… definend in the schema do not lanch the SQL to create the fulltext index.
Contributor
Author
Member
|
@marcellovetro you can close the old one now 😉 |
lauriejim
approved these changes
Sep 14, 2018
Contributor
lauriejim
left a comment
lauriejim
left a comment
There was a problem hiding this comment.
LGTM :) Thank you for this PR!
Member
|
Error still exists: |
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
4 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.
... If aren't text colums definend in the schema do not lanch the SQL to create the fulltext index that generate the following SQL Error:
My PR is a:
🐛 Bug fix
Main update on the:
Framework strapi-hook-bookshelf with Relational DBs such as MySql
New pull request from #1845