2.1. Major changes
Tigase Unified Archive component has undergone a few major changes to our code and structure. To continue to use Tigase Unified Archive component, a few changes may be needed to be made to your systems. Please see them below:
2.1.1. Database schema changes
We decided to no longer use in-code database upgrade to update database schema of Unified Archive component and rather provide separate schema files for every supported database.
Additionally we moved from in-code generated SQL statements to stored procedures which are now part of provided database schema files.
To continue usage of new versions of Unified Archive component it is required to manually load new component database schema, see Preparation of database section for informations about that.
Loading of new database schema is required to use new version of Unified Archive component.
2.2. New features
2.2.1. Support for using separate database for different domains
Since this version it is possible to use separate archived messages based on domains. This allows you to configure component to store archived message for particular domain to different database.
For more informations please look into [using separate store for archived messages]