Persistence
Field-by-field explanation of Identica's persistence configuration area.
The persistence configuration selects which database backend Identica uses and how the connection pool is configured.
By default, Identica falls back to SQLite when the persistence type cannot be resolved from an existing config.
type
- Takes:
"SQLITE","H2","MYSQL", or"POSTGRES" - Current default behavior: SQLite is the fallback backend
- Affects: which persistence backend class and JDBC URL strategy are used
Backend-specific fields
Different persistence types expose different fields.
Those backend-specific fields are normally generated after you switch type and restart the plugin.
If you only change type without letting the plugin boot again, the file structure may still reflect the old backend layout until Identica regenerates it.
file
- Takes: a file name or relative path
- Current default:
"identica.db" - Affects: the SQLite database file used under the plugin data directory
If this is blank, the runtime falls back to identica.db.
hikari
The hikari section controls the HikariCP connection pool used by the database layer.
For most setups, the defaults are a good starting point. You usually only change these values when you have a clear reason related to database load, connection limits, or infrastructure tuning.
poolName
Advanced- Takes: a string
- Current default:
"Identica" - Affects: the Hikari pool name shown in diagnostics and logs
maximumPoolSize
Advanced- Takes: an integer
- Current default:
10 - Affects: the maximum number of pooled database connections
minimumIdle
Advanced- Takes: an integer
- Current default:
2 - Affects: the minimum number of idle pooled connections Hikari tries to keep ready
connectionTimeout
Advanced- Takes: a number of milliseconds
- Current default:
30000 - Affects: how long Hikari waits for a connection before timing out
idleTimeout
Advanced- Takes: a number of milliseconds
- Current default:
600000 - Affects: how long idle pooled connections may stay unused before Hikari retires them
maxLifetime
Advanced- Takes: a number of milliseconds
- Current default:
1800000 - Affects: the maximum lifetime of a pooled connection before Hikari replaces it
Connection behavior
If the database connection cannot be established, Identica does not fail fast during Hikari initialization. Instead, it logs the connection problem and database-backed features remain unavailable until the connection can be established.