plasma / driver-mysql
The MySQL/MariaDB driver for Plasma.
Requires
- php: >=7.1
- ext-bcmath: *
- ext-mbstring: *
- evenement/evenement: ^3.0|^2.0
- obsidian/validation: ^0.1.0
- plasma/binary-buffer: ^0.1.0|dev-master
- plasma/core: ^0.4.0|^0.3.0|dev-master
- react/event-loop: ^1.0|^0.5|^0.4
- react/promise: ^2.7
- react/socket: ^1.1
- react/stream: ^1.0
Requires (Dev)
- ext-zlib: *
- clue/block-react: ^1.3
- phpunit/phpunit: ^7.0
- react/filesystem: ^0.1.2
- react/promise-stream: ^1.1
This package is auto-updated.
Last update: 2024-10-29 05:22:48 UTC
README
Plasma provides an asynchronous, non-blocking (data access) Database Abstraction Layer. This is the MySQL/MariaDB driver for Plasma.
The driver uses ReactPHP to asychronously interface with the database server.
The driver supports setting a connection charset through the driver options, it should be noted that the default is utf8mb4
(UTF-8), which is a character set you should use all the way through.
It should also be noted, that MySQL versions, which support the FOUND_ROWS
flag, can return a non-zero value when using StreamQueryResultInterface::getAffectedRows()
for SELECT
queries.
Getting Started
You can install this component by using composer
. The command is
composer require plasma/driver-mysql
After you've used composer to install the components and the dependencies, you get started by creating an instance of the factory.
The factory takes a loop instance and an array of options (see the factory class documentation for the available options).
The factory also gives you the ability to asychronously interface with the filesystem using react/filesystem
, if a LOCAL INFILE
request ever occurres.
Additionally you can create your own auth plugins, if your database server uses an authentication plugin this driver doesn't support (yet).
use Plasma\Client; use Plasma\Drivers\MySQL\DriverFactory; use React\EventLoop\Factory; $loop = Factory::create(); $factory = new DriverFactory($loop, array()); $client = Client::create($factory, 'user:password@localhost:3306/database', array()); // Code which uses the client to run queries against the database $loop->run();
Unix socket connections are supported using the unix://
scheme, so the example connect uri would look like this.
unix://user:password@localhost/database
When using unix socket connections without a database, a trailing slash is required. When using localhost
as unix socket path, the default mysql path will be used.
Cursors
MySQL supports cursors since 5.7 (MariaDB 10.3). As such the driver will reject MySQL versions below 5.7, respectively MariaDB 10.3, as they do not support cursors (even though the capabilities may say otherwise).
If known at driver method call time, the driver will throw a LogicException
, or postpone it and reject the promise with a LogicException
.
Compression
By default packet compression is enabled and all packets equal to or larger than 50 bytes are automatically compressed (as long as zlib is available).
This can be disabled using the compression.enable
flag.
Server OK Response Messages
The driver exposes every OK response message packet of the server through a Plasma Client event called serverOkMessage
. The argument is an instance of Messages\OkResponseMessage
.
As such advanced users can check the status of the server and perform certain actions, or just log it for pure statistics purposes.
Type Extensions
This driver uses a type extensions manager registered under the name driver-mysql
.
When decoding rows received from the database, the type extensions can get two different type of values to decode, depending on the used protocol.
When using the text protocol (regular queries), then the type extensions get the raw value as string.
However when using the binary protocol (prepared statements), then the type extensions get the used \Plasma\BinaryBuffer
instance.
It must be used with care. Reading too much from it can lead into dropped row, because the remaining fields can not be properly decoded.