CustomPdoDriverResultMiddleware implements Middleware, UsableForConnectionInterface
The `php-ext PDO` based pdo_* driver can return column data in query result sets as type `resource`, where the `mysqli` based driver returns type `string` instead. Dealing with data of type `resources`, for special driver, is not a well known technical detail in the broader php and TYPO3 developer community. Therefore, the TYPO3 core provided custom pdo_* driver implementation to provide a specific `DriverResult` class, which resolves this issue by converting type `resource` column data directly to string in `\TYPO3\CMS\Core\Database\Driver\DriverResult` within the method `mapResourceToString()` and uses it in the related methods.
With the Doctrine DBAL Driver Middleware features the custom drivers could be reduced and the required DriverResult
set added in a cleaner way. As this comes with minor performance impact, the custom DriverResult set needs to be
plumbed only to the absolutely required drivers - and the reason for the conditional usage restricted with method
canBeUsedForConnection().
this implementation is not part of TYPO3's Public API.
Tags
Table of Contents
Interfaces
- Middleware
- UsableForConnectionInterface
- Custom driver middleware can implement this interface to decide per connection and connection configuration if it should be used or not. For example, registering a global driver middleware which only takes affect on connections using a specific driver like `pdo_sqlite`.
Methods
- canBeUsedForConnection() : bool
- Return true if the driver middleware should be used for the concrete connection.
- wrap() : Driver
Methods
canBeUsedForConnection()
Return true if the driver middleware should be used for the concrete connection.
public
canBeUsedForConnection(string $identifier, array<string|int, mixed> $connectionParams) : bool
Parameters
- $identifier : string
- $connectionParams : array<string|int, mixed>
Return values
boolwrap()
public
wrap(Driver $driver) : Driver
Parameters
- $driver : Driver