-
Notifications
You must be signed in to change notification settings - Fork 99
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 script on production #5945
Fix migration script on production #5945
Conversation
16f43d0
to
dc41aaa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
Bors r+
Merge conflict. |
@mbayopanda, can you take a look at this merge conflict? |
dd9f9a8
to
490d597
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
I will test this on the IMCK database. In the mean time, I suggest check my comments on this review and then rebase.
* @author: mbayopanda | ||
* @desc: add predefined allocation basis | ||
*/ | ||
INSERT INTO `cost_center_allocation_basis` (`id`, `name`, `units`, `description`, `is_predefined`) VALUES |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: If PR #5947 gets merged first, this will need a little adjusting since I added items 1-3 in my version of migrate.sql. I suggest adding these (4-6) into the previous insert (with 1-3) above.
ALSO, please add the SQL 'IGNORE' keyword in your 'INSERT' statements.
490d597
to
a4e06b1
Compare
LGTM. bors r+ |
Build succeeded: |
This PR fixes migration script on a production data base by :
Also, some fix :