Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117858
MIME-Version: 1.0
Date: Mon, 6 Jun 2022 20:15:12 +0100
Message-ID: <CA+kxMuT54_xanhDr2ARceZhK2PrnQpJ0YrfX7rc3Ya4YJsbbpg@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: DB specific PDO subclasses questions.
From: Danack@basereality.com (Dan Ackroyd)

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#100813

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.

That is, are any of these functions horrible to use:

PDO::pgsqlCopyFromArray
PDO::pgsqlCopyFromFile
PDO::pgsqlCopyToArray
PDO::pgsqlCopyToFile
PDO::pgsqlGetNotify
PDO::pgsqlGetPid
PDO::pgsqlLOBCreate
PDO::pgsqlLOBOpen
PDO::pgsqlLOBUnlink

SQLIte specific functions:
PDO::sqliteCreateAggregate
PDO::sqliteCreateCollation
PDO::sqliteCreateFunction

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?

cheers
Dan
Ack