Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Not A Problem
-
2.0.13
-
None
-
None
Description
Start Syncope with PostgreSQL as DBMS and empty database and look at PostgreSQL logs. You'll se something like this
| 2019-08-30 13:00:07.420 UTC [67] ERROR: relation "qrtz_scheduler_state" does not exist at character 22 db-pg_1 | 2019-08-30 13:00:07.420 UTC [67] STATEMENT: SELECT COUNT(0) FROM QRTZ_SCHEDULER_STATE db-pg_1 | 2019-08-30 13:00:07.906 UTC [67] WARNING: there is no transaction in progress db-pg_1 | 2019-08-30 13:00:08.536 UTC [67] ERROR: relation "act" does not exist db-pg_1 | 2019-08-30 13:00:08.536 UTC [67] STATEMENT: SELECT pg_get_serial_sequence($1, $2) db-pg_1 | 2019-08-30 13:00:08.537 UTC [67] ERROR: relation "act_evt" does not exist db-pg_1 | 2019-08-30 13:00:08.537 UTC [67] STATEMENT: SELECT pg_get_serial_sequence($1, $2) db-pg_1 | 2019-08-30 13:00:08.538 UTC [67] ERROR: column "log_nr" of relation "act_evt_log" does not exist db-pg_1 | 2019-08-30 13:00:08.538 UTC [67] STATEMENT: SELECT pg_get_serial_sequence($1, $2) db-pg_1 | 2019-08-30 13:00:08.539 UTC [67] ERROR: relation "act_evt_log_log" does not exist db-pg_1 | 2019-08-30 13:00:08.539 UTC [67] STATEMENT: SELECT pg_get_serial_sequence($1, $2) db-pg_1 | 2019-08-30 13:00:08.544 UTC [67] ERROR: relation "act" does not exist db-pg_1 | 2019-08-30 13:00:08.544 UTC [67] STATEMENT: SELECT pg_get_serial_sequence($1, $2) db-pg_1 | 2019-08-30 13:00:08.545 UTC [67] ERROR: relation "act_evt" does not exist db-pg_1 | 2019-08-30 13:00:08.545 UTC [67] STATEMENT: SELECT pg_get_serial_sequence($1, $2) db-pg_1 | 2019-08-30 13:00:08.545 UTC [67] ERROR: column "log_nr" of relation "act_evt_log" does not exist db-pg_1 | 2019-08-30 13:00:08.545 UTC [67] STATEMENT: SELECT pg_get_serial_sequence($1, $2) db-pg_1 | 2019-08-30 13:00:08.546 UTC [67] ERROR: relation "act_evt_log_log" does not exist