-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mysql.index is not work on property #467
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
@property({type: 'string', mysql: {index: {kind: "FULLTEXT"}}})
on model.npm run migrate
on cli.This is example of a model.
Current Behavior
@property.mysql.index
is not work.But, I see work with
@property.index
.Expected Behavior
We can replace
@property.mysql.index
with@property.index
on README.loopback-connector-mysql/README.md
Lines 535 to 545 in f8f40a1
Or,
Fix the
prop.index
toprop.mysql.index
andm.properties[propName].index;
tom.properties[propName].mysql.index;
on migration.js.loopback-connector-mysql/lib/migration.js
Line 661 in f8f40a1
loopback-connector-mysql/lib/migration.js
Line 361 in f8f40a1
Link to reproduction sandbox
https://github.com/forno/loopback-next/blob/index-bug-report/examples/todo/src/models/todo.model.ts
Additional information
the index creation function are already exist. But it is different config written by README.
I don't know that either is correct.
Related Issues
#350
See Reporting Issues for more tips on writing good issues
The text was updated successfully, but these errors were encountered: