XAMPP commonly includes a MariaDB database server and phpMyAdmin, although the exact bundled versions vary by release. The control-panel label may still say MySQL. For reliable development, identify the actual server and version rather than relying on the label.
Verify the database engine
Start the database service from the XAMPP Control Panel. Open phpMyAdmin and inspect the server information, or connect from the command line and run SELECT VERSION();. Record the engine and version so schema behavior can be compared with the production database.
Create a project database and user
Create a database with the character set and collation used by the application. Create a separate local database user with privileges limited to that database. Avoid reusing a broad administrative account in application configuration. Store credentials in an ignored environment file, not in a public PHP file.
Understand phpMyAdmin's role
phpMyAdmin is a browser-based administration client; it is not the database server itself. Use it for inspecting tables, running controlled SQL and importing or exporting development data. Large imports may be constrained by PHP upload limits and execution time. For larger dumps, use the database command-line client where available.
Keep local and production compatible
MySQL and MariaDB are related but not identical products. SQL syntax, JSON behavior, collations, generated columns and optimizer behavior can differ by version. Test migrations against the same engine family and a close version match to production. Do not assume a dump created on a newer server will import unchanged on an older one.
Protect local data
Do not expose phpMyAdmin to the public internet. Keep local services bound to loopback where practical, use strong credentials and avoid importing real customer data unless it has been properly anonymized.
Further reading
- MariaDB documentation: https://mariadb.com/kb/en/documentation/
- phpMyAdmin documentation: https://docs.phpmyadmin.net/