Skip to content

javascript: add packaging of 1st party drivers (postgresql, sqlite, flightsql) #4414

Description

@H-Plus-Time

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions