[New Driver] Propose adding a Presto (PrestoDB) driver

[jja725]

Summary

I'd like to propose adding a Presto (PrestoDB) driver to the ADBC Driver
Foundry, following the same pattern as the existing Trino
driver: a standalone repo built on
driverbase-go, wrapping a database/sql client
(prestodb/presto-go-client/v2)
via sqlwrapper.

I've built a working prototype at
https://github.com/jja725/adbc-presto by porting the Trino driver's
structure over to the Presto client, and would like to either transfer this
repo into the org (e.g. as adbc-drivers/presto) or use it as the basis for
a fresh PR into a new org repo, whichever the maintainers prefer.

Status

• Mirrors the adbc-drivers/trino layout: driver core, db_factory.go,
  catalog/schema/statistics introspection, error mapping, cgo shared-library
  packaging (pkg/), a docker-compose + pytest validation suite, and CI
  workflow templates adapted from adbc-drivers/dev.
• Builds and passes go vet/gofmt cleanly, plus the cgo shared library
  (-tags driverlib -buildmode=c-shared).
• Full Go integration suite (validation + driver-specific tests, 85 cases)
  passes against prestodb/presto:latest (0.298) in Docker.

Notable differences from the Trino driver (why this isn't just a rename)

• No current_catalog/current_schema SQL functions in PrestoDB, and
  the Go client doesn't apply X-Presto-Set-Catalog/Schema response
  headers to its session. The driver tracks the current namespace itself
  (validated against system.metadata.catalogs /
  information_schema.schemata) and applies it to new pooled connections
  via presto.WithSessionSetup.
• PrestoDB does not narrow INSERT literals (e.g. an INTEGER literal
  is rejected for a TINYINT column), so the ingest path wraps
  TINYINT/SMALLINT/REAL/DECIMAL/TIME/DATE/TIMESTAMP WITH TIME ZONE
  parameters in explicit CASTs.
• Presto TIMESTAMP/TIME have fixed millisecond precision (no
  parameterized precision like Trino), and the client exposes no
  precision/scale/nullability column metadata, so DECIMAL maps to
  string and ARRAY/MAP/ROW map to JSON strings.
• SHOW STATS has an extra histogram column in PrestoDB; the scan
  tolerates either column count.
• Error mapping targets presto.QueryError (ErrorType/ErrorName/code
  ranges) and HTTP-level presto.ErrorResponse, since PrestoDB doesn't
  return SQLSTATE.

Open questions for maintainers

1. Preferred path: transfer jja725/adbc-presto into the org, or open a PR
   against a freshly-created empty adbc-drivers/presto repo?
2. Module path / driver naming conventions to follow exactly (I used
   github.com/adbc-drivers/presto, driver name presto, matching the
   adbc-drivers/trino conventions).
3. Any preference on how a PrestoDB driver should relate to the existing
   presto-go-client/v2's dual Presto/Trino support — I kept this driver
   PrestoDB-only and left Trino on trino-go-client in the existing driver,
   since the latter has richer Trino-specific features (typed array
   scanning, progress callbacks, prepared statements) that the shared
   client doesn't provide.

Happy to open the PR once there's a repo to target, or adjust the structure
based on feedback here first.

[lidavidm]

Hi @jja725, a separate Presto driver seems reasonable. Are you thinking you'd like to continue maintaining this? (We can grant maintainer-level privileges.) Is there any interest from the Presto project itself?

[lidavidm]

We can copy the repo and make any adjustments. I don't think we'd advertise any support for Trino. I'd also need to check over the repo quickly before copying.

[jja725]

Hi @lidavidm yes I would love to maintain this as a open source project and collaborate on the Presto side as a open source community collaboration.

[lidavidm]

Thanks - let me follow up. I'll check things over / create a repo / etc.

[lidavidm]

By the way - have you reached out to the Presto maintainers at all?

[lidavidm]

And do you know what's going on with https://github.com/prestodb/rfcs/blob/main/RFC-0022-go-client-v2.md? I can't find the v2 repo, but it doesn't sound promising that we're using a deprecated client.

[lidavidm]

Anyways, I've made a repo and sent you an invite @jja725. It will be private while we set things up and will be made public later.

[jja725]

Hi @lidavidm , I already talked to @ethanyzhang and he would take a look at the design as well. In the meantime we can start setting up the basic repo. We still use the same repo but it's with v2 version