DATABASE DRIVER

Move a node from the SQLite profile to MySQL/MariaDB.

PBE chooses the storage backend from the database section of config/config.php. Standalone builds normally use SQLite; web/server deployments use MySQL or MariaDB.

1. Prepare MySQL/MariaDB

Create a dedicated PBE database and a least-privilege database user for the node. Do not reuse an administrative database account. PBE's MySQL runtime schema is represented by database/schema.mysql.runtime.sql.

2. Change the database configuration

PHP

'database' => [
    'driver' => 'mysql',
    'host' => '127.0.0.1',
    'database' => 'pbe',
    'user' => 'pbe',
    'password' => 'USE_A_REAL_LOCAL_SECRET',
],

Remove the SQLite path entry when the MySQL driver is selected. Keep the actual password only in the local active configuration.

3. Initialize/validate the release schema

Use the 0.0.1 MySQL runtime schema and start the node against that database. The storage layer validates release-era columns and refuses incompatible schema revisions rather than treating an older database as current.

4. Start and synchronize

Shell

php bin/pbe-node --config config/config.php

Verify PBE-MAINNET, network ID 1, protocol 1.0 and the frozen mainnet genesis identity before relying on the new backend.

Do not copy SQLite bytes into MySQLChanging the driver does not turn a SQLite file into a MySQL database. PBE 0.0.1 documentation does not assume an automatic cross-database conversion tool. Preserve the old SQLite file as a backup and use a properly initialized MySQL database, then let the node synchronize canonical chain state from compatible peers unless you have a separately verified migration procedure.

When MySQL makes sense

SQLite is appropriate for a single local standalone process. MySQL/MariaDB is the intended profile for higher-concurrency public web deployments, long-running hosted nodes, and environments already operating a managed database service.