 |
The behavior is exiting in case of error when ExitOnFatal = true STATEMENT: DROP TABLE temp ERROR: table "temp1" does not exist this is an error and the product the obey strictly to the paramet Exit On Fatal. Now with future version, where only postgresql will be kept as database, but also older postgresql will never be installed the code can be reviewed to chase every drop table without and if exist. Files to change ``` core/src/cats/dml/0018_uar_del_temp:DROP TABLE temp core/src/cats/dml/0019_uar_del_temp1:DROP TABLE temp1 core/src/cats/mysql_queries.inc:"DROP TABLE temp " core/src/cats/mysql_queries.inc:"DROP TABLE temp1 " core/src/cats/postgresql_queries.inc:"DROP TABLE temp " core/src/cats/postgresql_queries.inc:"DROP TABLE temp1 " core/src/cats/sqlite_queries.inc:"DROP TABLE temp " core/src/cats/sqlite_queries.inc:"DROP TABLE temp1 " core/src/dird/query.sql:!DROP TABLE temp; core/src/dird/query.sql:!DROP TABLE temp2; ``` Do you want to propose a PR for ? |
|
|
PR proposed https://github.com/bareos/bareos/pull/1035 Once the PR will be build, there's will be some testing package available, would you like to test them ? |
|
|
Hi, thank you for looking into this issue! I will try to test the built package (deb preferred) if a subsequent code/package "downgrade" (ie. no Catalog DB changes, ...) to a published Community Edition release remains possible afterwards. |
|
|
Fix committed to bareos master branch with changesetid 15753. |
- Anonymous
