Skip to content
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

fix(migration): foreign key length correction #2498

Merged
merged 2 commits into from Jun 30, 2022

Conversation

pranavxc
Copy link
Member

Change Summary

Foreign key length correction in migration file.

Change type

  • feat: (new feature for the user, not a new feature for build script)
  • fix: (bug fix for the user, not a fix to a build script)
  • docs: (changes to the documentation)
  • style: (formatting, missing semi colons, etc; no production code change)
  • refactor: (refactoring production code, eg. renaming a variable)
  • test: (adding missing tests, refactoring tests; no production code change)
  • chore: (updating grunt tasks etc; no production code change)

re #2201

Signed-off-by: Pranav C <pranavxc@gmail.com>
@pranavxc pranavxc added the 🛑 Status: Do Not Merge Used in PR only. The PR cannot be merged due to some reasons. label Jun 28, 2022
- Dropping existing column won't cause any problem since it only contains boolean value and which is not useful

Signed-off-by: Pranav C <pranavxc@gmail.com>
@pranavxc pranavxc added this to the Next Release : v0.92.x milestone Jun 30, 2022
@pranavxc pranavxc removed the 🛑 Status: Do Not Merge Used in PR only. The PR cannot be merged due to some reasons. label Jun 30, 2022
@pranavxc pranavxc merged commit 035698e into develop Jun 30, 2022
@pranavxc pranavxc deleted the fix/mssql-noco-migration-error branch June 30, 2022 05:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants