4. The Entity Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1. Entity Engine guide.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.2. Entity Engine Configuration Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.7. Entity engine configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4. Entity Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.3. Entity engine configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 5. Service Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4. The Entity Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1. Entity Engine guide.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.2. Entity Engine Configuration Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.7. Entity engine configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4. The Entity Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1. Entity Engine guide.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.2. Entity Engine Configuration Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.7. Entity engine configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in underlaying version control permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching

Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in underlaying version control permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching

Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in underlaying version control permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching

Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in underlaying version control permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching

Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in underlaying version control permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching

Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in the underlaying version control permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching