The “SQLite” driver of PDO is missing some features provided by the “SQLite3” extension, namely “openBlob” which allows to access a stored blob as a stream/file pointer.
As discussed on internals the SQLite driver of PDO is missing some features that are present in the SQLite3 extension.
One of those features has already been proposed and merged: Add support for SQLite open flags.
A second one has been proposed and is awaiting merging: Implement sqlite_stmt_readonly in PDO
But we are still missing this feature: SQLite3::openBlob: opening blobs for reading and writing as streams.
This would be implemented following the current practice of adding a driver-specific method:
PDO::sqliteOpenBlob(string $table , string $column , int $rowid [, string $dbname = “main” [, int $flags = PDO::SQLITE_OPEN_READONLY ]] )
This would return a resource file pointer. This would match exactly the behaviour of SQLite3::openBlob.
This is following what already exists in PDO, examples:
These driver-specific methods are only defined when instantiating PDO with the right driver, trying to call them with another driver results in an error due to calling an undefined method.
For reference: http://www.php.net/manual/en/pdo.lobs.php
As this was discussed on internals, the PDO LOB support is for accessing LOB using SQL queries, openBlob is for accessing LOBs directly. This is a very fast and efficient way of using SQLite as a blob store, which can't be done if going through SQL queries as traditional PDO::PARAM_LOB support is doing. Furthermore, openBlob allows to both read and write in a blob at the same time. And finally the current code handling LOBs in PDO via bindParam and bindColumn is broken, it is returning a string (with MySQL and SQLite, but not PostgreSQL) instead of a resource file pointer. I will try to spend time fixing that in the coming months.
In conclusion this new method and the existing PDO LOB support provide different features for different needs, and both are useful.
None.
PHP 7.3
None.
None.
None.
None.
None.
None so far.
Nothing else is affected.
Any proposal to review and change current style and behaviour of driver-specific methods in PDO. This is out of the scope of this proposal.
This proposal requires a 50%+1 majority. Vote closing on Oct 27, 2017.
After the project is implemented, this section should contain
Keep this updated with features that were discussed on the mail lists.