SQLite Testing

View source for Issues to consider

  1. For advanced search capabilities, MySQL or MariaDB are strongly recommended.
  1. The decision to use SQLite should ideally be made before creating the wiki, as migrating from SQLite to MySQL later is difficult.
  1. The database file is typically stored in a directory outside the web root.
    1. ##../data/db_name.sqlite##
  1. To ensure optimal performance, the database should be configured in WAL (Write-Ahead Logging) mode.
    1. ##PRAGMA journal_mode=wal;##
  1. For full text search functionality, SQLite must be compiled with the FTS5 module, which is commonly included in modern builds.
  1. Access control is handled through the file-system permissions of the database file.
  1. SQLite requires that index names be unique across the entire database, not just within a single table.
  1. The entire database is stored in a single file, which simplifies backup procedures. If the database is offline, a simple file copy suffices for backup.
  1. A SQLite database file should not be used for more than one wiki. The cache table could be inserted into an additional database file.