H-Plus-Time opened a new issue, #4414: URL: https://github.com/apache/arrow-adbc/issues/4414
### What feature or improvement would you like to see? My thinking here would be to piggyback on the build process for the python wheels (which vendor in things like libpq - the node ecosystem has similar conventions) and package them up mechanically as: ``` @apache-arrow/adbc-driver-postgresql/ ├── package.json ├── index.js // containing `getDriverPath` and `getDriverManifestPath` (if that's desirable) // platform-dependent packages @apache-arrow/adbc-driver-postgresql-linux-x64/ ├── package.json ├── libadbc_driver_postgresql.so └── manifest.toml // dependent on whether distributing driver manifests is a good idea ``` Is there any desire for a direct dbapi-like interface for the per-driver packages (wherein you can import the driver package directly and connect via that), or should the behaviour be left the same as for the C, R and Go libraries? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
