What do you want to know? MySQL syntax documentaiton: https://dev.mysql.com How to use MySQL from plugins: examples available in many plugins How to use MySQL with libasynql, which is probably the easiest way to make plugins use MySQL asynchronously (so that it won't lag the server): https://github.com/poggit/libasynql Anything else?
Code: Warning: Use of unshaded libasynql detected. Debug mode is enabled. This may lead to major performance drop. Please use a shaded package in production. See https://poggit.pmmp.io/virion for more information.
Yes. Libasynql is on debug mode if it is unpackaged, and extra tasks are run on debug mode and decrease performance. In production, you should pack your plugin (without libasynql) into a phar, then run Code: php libasynql.phar plugin.phar 'your\plugin\namespace' (no need '' if you are on Windows) to compile the plugin. Or just use the Poggit build in production
MySQL schema is a section of your MySQL server. You can think of it as a directory inside your MySQL database. Before you start the server with the plugin, you should first run the MySQL query (in a MySQL client) to create a schema: Code: mysql> CREATE SCHEMA your_schema_name; The schema name is usually the plugin name, because different plugins may have the same table name, and it is important to make sure these plugins won't conflict with each other.
libasynql is a virion, not a plugin. A virion should be bundled along with your plugin. You should not ask your users to download libasynql separately, because it should be included inside the phar.
Read the virion guide: https://poggit.pmmp.io/virion Anything that works is ok for your own development. But make sure not to tell users to do that when you release the plugin as a phar.