Fix Restore

Summary

An old passwords table still existed in current dumps and created problems.

Focus

Remove the table if it exits. See #47

Test Environment

unit tests

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related issues
• Up-to-date CHANGELOG.md (or not necessary)
• Up-to-date JSON schema (or not necessary)
• Appropriate user and developer documentation (or not necessary)
  • How do I use the software? Assume "stupid" users.
  • How do I develop or debug the software? Assume novice developers.
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md (or not necessary)
• Appropriate user and developer documentation (or not necessary)
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there specifications? Are they satisfied?

For further good practices have a look at our review guidelines.

patches/patch20221122-6.0-SNAPSHOT/patch.sh

@@ -25,6 +25,8 @@
 NEW_VERSION="v6.0.0-SNAPSHOT-EXTIDS"
 OLD_VERSION="v5.0.0"
 
+DROP_TABLE_PASSWORDS='DROP TABLE IF EXISTS passwords;'
+
 if [ -z "$UTILSPATH" ]; then
  UTILSPATH="../utils"
 fi
@@ -33,9 +35,11 @@ fi
 
 check_version $OLD_VERSION
 
+mysql_execute "$DROP_TABLE_PASSWORDS"
 mysql_execute_file $PATCH_DIR/create_entity_ids_table.sql
 
 update_version $NEW_VERSION
 
+
 success
 

[Henrik tom Wörden]

We cannot create a new patch, because this patch would not work without this change