YAS Currency

YASCurrency v1.3.0 - Optional MariaDB Storage & Migration Finalization

This update finalizes the optional MariaDB storage path for YASCurrency while keeping SQLite as the default and recommended backend for most servers.

Added

• Added optional MariaDB storage backend.
• Added storage backend abstraction so YASCurrency can use SQLite or MariaDB through the same economy service layer.
• Added MariaDB configuration options:

  storage.type=mariadb
  mariadb.host=localhost
  mariadb.port=3306
  mariadb.database=yascurrency
  mariadb.username=yascurrency
  mariadb.password=change-me
  mariadb.useSsl=false
  mariadb.connectionTimeoutMs=5000
  mariadb.autoCreateTables=true

• Added automatic MariaDB table creation when the target database already exists and mariadb.autoCreateTables=true is enabled.
• Added /yascurrency storage test command for detailed backend diagnostics.
• Added /yascurrency storage status command for quick storage status checks.
• Added /yascurrency storage migrate sqlite-to-mariadb command.
• Added explicit SQLite to MariaDB migration support.
• Added SQLite backup creation before migration.
• Added migration import for accounts, transactions, and metadata.
• Added migration comparison checks for account count, transaction count, and total money supply.
• Added MariaDB schema validation during startup and diagnostics.
• Added storage backend information to admin health output.
• Added startup logging for the active storage backend and storage description.
• Added MariaDB setup and migration documentation.

Changed

• SQLite remains the default storage backend.
• MariaDB is now available as an optional backend for larger servers, hosted setups, and externally managed database environments.
• YASCurrency no longer depends directly on the SQLite implementation in the main currency service.
• Admin storage health now uses a cached storage snapshot to reduce repeated database work.
• Admin UI performance has been improved when switching between tabs.
• Storage health output now clearly shows whether SQLite or MariaDB is active.
• Migration results now clearly explain that YASCurrency does not automatically switch to MariaDB after migration.
• The storage help/usage output now includes the new storage diagnostic and migration commands.
• Config comments now explain the difference between SQLite default storage and optional MariaDB storage.

Improved

• Improved MariaDB error messages for common setup problems.
• Improved feedback when the MariaDB database is missing.
• Improved feedback when MariaDB credentials are incorrect.
• Improved feedback when required MariaDB tables are missing and automatic table creation is disabled.
• Improved feedback when MariaDB permissions are insufficient.
• Improved warning messages when the MariaDB target database is not empty.
• Improved admin guidance after a successful SQLite to MariaDB migration.
• Improved backend safety by avoiding silent fallback to SQLite when MariaDB was explicitly selected.
• Improved admin tab responsiveness by avoiding unnecessary repeated storage checks.
• Improved documentation for server administrators who want to use MariaDB.

Migration Guide Summary

To migrate from SQLite to MariaDB:

1. Create the MariaDB database and database user manually.
2. Configure the MariaDB connection settings in the YASCurrency config.
3. Keep storage.type=sqlite active for the migration step.
4. Run:

   /yascurrency storage migrate sqlite-to-mariadb

5. Review the migration result.
6. If the result is OK, set:

   storage.type=mariadb

7. Restart the server.
8. Verify the active backend with:

   /yascurrency storage test

Important Notes

• SQLite is still the default. Existing servers do not need to change anything.
• MariaDB is optional. Only enable it if you want to use an external database backend.
• The MariaDB database and database user must be created by the server administrator.
• YASCurrency can create the required tables inside the existing MariaDB database when automatic table creation is enabled.
• The migration command does not automatically switch the active backend.
• After a successful migration, admins must manually set storage.type=mariadb and restart the server.
• For most small or single-server setups, SQLite remains the easiest and recommended option.