(Redmine issue: #3361)

(Redmine issue: #3443)

(Redmine issue: #3443)

Refactoring: Renamed HawatBlueprint -> VialAppBlueprint, HawatUtils -> VialAppUtils, code style improvements.

(Redmine issue: #3443)

(Redmine issue: #3443)

(Redmine issue: #3443)

The name 'HAWAT' was omitted wherever possible to make names shorter.

(Redmine issue: #3387)

* If none of the following search parameters (dt_from, dt_to, st_from, st_to) is present in the URL, provide default dt_from (last 7 days) to reduce amount of processed events.
* User still has the ability to perform unbound search by submitting empty form.

(Redmine issue: #4609)

(Redmine issue: #3387)

Added logging or request.path_full to enable better debugging of BAD REQUEST and INTERNAL SERVER ERROR errors.

(Redmine issue: #6232)

As it turned out the timepager component was modifiing request parameters to generate the links and subsequent components were unable to access original values. (Redmine issue: #4609)

(Redmine issue: #3387)

After encountering StorageIntegrityError it was possible for savepoint not to exist and subsequent attempts for storing events to database failed. This patch is a hotfix, the solution is not optimal, because the create_savepoint primitive is called before and after storing event into database.

* Support for almost full event search form (except page, limit and searchby parameres, which do not make sense).
* Redirection from Timeline search result page to Event search page and vice versa.
(Redmine issue: #4609)

(Redmine issue: #4489)

(Redmine issue: #4489)

(Redmine issue: #4489)

(Redmine issue: #3387)

Vacuum command may not be executed within transaction.

(Redmine issue: #3387)

To better understand what went wrong with the request. (Redmine issue: #3443)

According to our current production installation. (Redmine issue: #3387)

(Redmine issue: #3387)

* Added script for turning maintenance mode ON/OFF.
* Updated documentation to include new maintenance mode script.

(Redmine issue: #6096,#3361)

It was pointed out, that PostgreSQL database optimizations will be more usefull in ready-to-use executable script than in documentation page. This commit introduces very basic script with the list of suggested database optimizations. (Redmine issue: #6096)

PostgreSQL does not like connections being closed and reopened again. (Redmine issue: #4251)

(Redmine issue: #4251)

Radko Krkoš authored 5 years ago and Jan Mach committed 5 years ago

* This makes the ORM query handling to be in line with SQLAlchemy's design and expectations.

(Redmine issue: #4251)

(Redmine issue: #6096)

To be consistent with the rest of the system. SQLAlchemy ORM model does not allow to specify ALTER TABLE commands for models. Therefore it would be necessary to run migrations after clean installation, which could cause chaos and troubles with schema versions and stamping. I have moved the cluster commands to database optimization documentation, which is where they belong. (Redmine issue: #6096)