MDL-77988 dml: correct logic when dropping plugin tables.

Comparison of method void return within a conditional didn't make
sense, and the aforementioned method throws an exception on error
anyway which would halt execution.
This commit is contained in:
Paul Holden 2023-06-19 15:51:59 +01:00
parent cccc00954d
commit 28e1bd37d0
No known key found for this signature in database
GPG Key ID: A81A96D6045F6164
2 changed files with 3 additions and 1 deletions

View File

@ -370,7 +370,8 @@ function drop_plugin_tables($name, $file, $feedback=true) {
global $CFG, $DB;
// first try normal delete
if (file_exists($file) and $DB->get_manager()->delete_tables_from_xmldb_file($file)) {
if (file_exists($file)) {
$DB->get_manager()->delete_tables_from_xmldb_file($file);
return true;
}

View File

@ -21,6 +21,7 @@ information provided here is intended especially for developers.
- `\core\encryption::METHOD_OPENSSL`
- `\core\encryption::OPENSSL_CIPHER`
* The `\core\encryption::is_sodium_installed` method is deprecated, as Sodium is now a requirement
* The `drop_plugin_tables` method now returns immediately after deleting tables defined by plugin XMLDB file
* Support for the following phpunit coverage info properties, deprecated since 3.11, has been removed:
- `whitelistfolders`
- `whitelistfiles`