-
Notifications
You must be signed in to change notification settings - Fork 56
Issue #128 #142
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
Issue #128 #142
Conversation
@morehappiness could you please squash the changes in single commit? These change are potentially breaking, so I would like to revert them with single commit. |
Apologies, @morehappiness I didn't saw that you already had the squashed commit. I just saw the 28 files changed. |
@morehappiness we would the sql script to migrate the schema to have |
What do you mean by ' squashed commit'? Yes, I will add deletedBy column in sql script |
@vikasrohit , do you mean to commit to branch 'feature/timeline-milestone-issue#128-soft-delete' |
It seems that the new tables in 20180608_project_add_templateId_and_new_tables.sql already have the deletedBy column. But i do not see the table definition for projects, project_attachments, project_members |
Squashed means, single commit for the change which you have already done. Thank you.
No, that I created in assumption that you have committed more than 1 commit for the change. But it is not needed now as you have already committed only single commit.
Yes, those are missing as initially the project used sequelize sync method to create the tables in database even on production which have stopped using later to avoid unwanted db migrations automatically. You can add a new migration SQL with today's date and just add the alter commands needed to add the new columns to the tables. |
i see the pull request has been accepted. Do you still need the projects, project_attachments, project_members to add deletedBy column for migration? |
I created it. I think we are good now. |
Fix Issue #128