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

Back up SQL from cleanup_mri_tables_for_19-0_release.php saved in project/backup now #3483

Merged
merged 2 commits into from
Feb 19, 2018

Conversation

cmadjar
Copy link
Collaborator

@cmadjar cmadjar commented Feb 12, 2018

This pull request allows the cleanup_mri_tables_for_19-0_release.php script to save the backup SQL file in project/backup as suggested in PR #3473 by @ridz1208.

Should add in the release that the backup SQL created by the script will be located in project/backup.

@ridz1208 I put you as a reviewer for this PR. Let me know if that works.

@cmadjar cmadjar added Cleanup PR or issue introducing/requiring at least one clean-up operation Language: SQL PR or issue that update SQL code Release: Document at release PR whose changes need to be documented in the wiki (or other documentation) at release Critical to release PR or issue is key for the release to which it has been assigned labels Feb 12, 2018
@cmadjar cmadjar added this to the 19.0 milestone Feb 12, 2018
@cmadjar cmadjar requested a review from ridz1208 February 12, 2018 17:58
PapillonMcGill
PapillonMcGill previously approved these changes Feb 12, 2018
@@ -263,6 +263,11 @@ function backupEntries($selectID, $table_name, $FK_field)
$IDs = generateIdList($selectID, $FK_field);
$where = $FK_field . " IN (" . $IDs . ")";

// create directory where the back up will go if it does not exist yet
if ( !file_exists("../project/backup") ) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these should include the __DIR__ see line 273

otherwise someone running it from another directory than tools would have issues

@cmadjar
Copy link
Collaborator Author

cmadjar commented Feb 12, 2018

@ridz1208 Oups... Thanks. Should be fixed now.

ridz1208
ridz1208 previously approved these changes Feb 12, 2018
@driusan
Copy link
Collaborator

driusan commented Feb 16, 2018

@cmadjar can you rebase this now that Travis is fixed?

@ridz1208
Copy link
Collaborator

@driusan @cmadjar I'll do it

@ridz1208 ridz1208 force-pushed the WriteSqlInProjectBackupFolder branch from 80b0c6d to eda1f89 Compare February 16, 2018 20:59
@ridz1208
Copy link
Collaborator

@driusan rebase and tested

@ridz1208 ridz1208 added the Passed manual tests PR has been successfully tested by at least one peer label Feb 16, 2018
@driusan driusan merged commit 49b6261 into aces:19.0-dev Feb 19, 2018
@cmadjar cmadjar deleted the WriteSqlInProjectBackupFolder branch April 9, 2018 13:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Cleanup PR or issue introducing/requiring at least one clean-up operation Critical to release PR or issue is key for the release to which it has been assigned Language: SQL PR or issue that update SQL code Passed manual tests PR has been successfully tested by at least one peer Release: Document at release PR whose changes need to be documented in the wiki (or other documentation) at release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants