sqlalchemy-trino
sqlalchemy-trino copied to clipboard
dungdm93
Trino (f.k.a PrestoSQL) dialect for SQLAlchemy.
It seems like the [official Trino Python DB API client](https://github.com/trinodb/trino-python-client) now supports [SQLAlchemy bindings](https://github.com/trinodb/trino-python-client#sqlalchemy) and was wondering whether this package should be deprecated?
Originally filed as https://github.com/sqlalchemy/sqlalchemy/issues/7905 ### Describe the use case Here is an issue filed against Pandas that connects to a Trino database and yields a bad result when using SQLAlchemy:...
Hello, Since SQLAlchemy 1.4.5 it is required from third party dialects to set whether they comply with statement cache with `supports_statement_cache` attribute. More details in the [docs](https://docs.sqlalchemy.org/en/20/core/connections.html#caching-for-third-party-dialects). If the attribute...
Add support for args/params for extraCredentials to be passed via headers to trino Thinking this link may be of use: https://github.com/dropbox/PyHive/issues/311#issuecomment-586828649
Hi, the following code failed with Error `TypeError: can't pickle PyCapsule objects` ``` auth = trino.auth.KerberosAuthentication(service_name=KerberosRemoteServiceName,principal=principal, ca_bundle=ca_bundle) from sqlalchemy.engine import create_engine engine = create_engine( f'trino://{username}@{presto_host}:{presto_port_ssl}/', connect_args={'auth': auth, 'http_scheme':protocol, 'catalog':catalog}, )...
proposed implementation for #39 This implements the proposal to parse the sqlalchemy standard `schema` kw arg to find embedded `catalog.schema` values
Currently the only way I know to tell sqlalchemy-trino about trino catalog name is in the connection url. That works pretty well but it would be conceptually cleaner to support...
Hi, we are using Trino with Superset and Iceberg to process and persist our data. We found out that when we use data backed by Iceberg, which's schema contains a...
parsing for rows would fail with `row(x timestamp(6) with time zone)` This because the driver would not expect extra parameters Adding both a fix and a test to check if...
The current implementation will keep using default TCP port number `8080` from underneath DB-API driver even using HTTPS: https://github.com/dungdm93/sqlalchemy-trino/blob/5aea36225cb8352cede5df4499b7d9628011ae50/sqlalchemy_trino/dialect.py#L92-L94 However, this could be documented or it will fail the connection...
