Re: DB specific PDO subclasses questions.
| From: | Matteo Beccati | Date: | Tue, 07 Jun 2022 08:17:04 +0000 |
| Subject: | Re: DB specific PDO subclasses questions. | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-117862@lists.php.net to get a copy of this message | ||
Hi Dan,
On 06/06/2022 21:15, Dan Ackroyd wrote:
Hi, I'm looking at making an RFC for subclassing PDO to expose database specific methods in a less magic way, aka implementing what was discussed here: https://externals.io/message/100773#100813Oh, that was a long thread! Not sure what the RFC goal would be, but I'm happy to discuss :)
I have two questions for people who use the PDO with SQLite or Postgres 1. Are any of the functions that are specific to those databases horribly designed and need changing? As the functions would be 'copied across' from where they are now, changes could be made without having horrible BC breaks.I will check, but...
That is, are any of these functions horrible to use:[snip] Not that I know of.
2. Other than the SQLite blobOpen functionality, does anyone know of any other functionality that is exposed by SQLite or Postgres that isn't currently exposed through the magic PDO methods?ext/pgsql has plenty of low level functions, e.g. for connection management, more large-object functionality and has async functionalities. For various reasons, none of them seem a good fit for PDO to me: - connection management: a common interface would be best - large objects: mostly obsolete functionality, a PITA to work with - async: better to leave that for PDO2, PDO-ng or PDO++ ;-) Cheers -- Matteo Beccati Development & Consulting - http://www.beccati.com/