Releases: mara/mara-db
Releases · mara/mara-db
4.11.0
4.10.0
4.9.2
4.9.1
4.9.0
Breaking Changes
- the implementation of the formats option (#56) required to do changes to the functions in
mara_db.shell
. In case you defined custom implementations, you will have to adjust them.
Feat 🎉
- adding a functional API to get the DB-API 2.0 of a database (#71)
- add option to specify multiple formats like Parquet, Avro and ORC (#56, #64)
Changes 🚀
- refactor the internally used cursor context logic to a more generic one (#68, #71)
- a default database
mara
is not anymore defined (#67). - add deprecation warning when using parameter
timestamp
in query_command. This parameter will be removed in version 5.0. See #44.
Bugfixes 🐛
- fix sqlalchemy_url for SQLServerDB
- fix UI error when requesting schema view for Azure Synapse databases (#48)
4.8.0
Breaking Changes
- when using BigQuery you need to rename the BigQueryDB db config parameter
service_account_private_key_file
toservice_account_json_file_name
(#45) - when using BigQuery with copy/read operations you need to specify parameter
gcloud_gcs_bucket_name
in the BigQueryDB db config (#45)
Feat 🎉
- Add Databricks db support (#62)
- Add Snowflake db support (#52/#61)
- Add sqlalchemy support for BigQuery (#45/#50)
- Add sqlalchemy support for SQL Server (#46)
- Add option to use either MSSQL Tools (sqlcmd/bcp) or sqsh to connect to SQL Server (#57)
- Add documentation readthedocs.io documentation (#59)
Changes 🚀
- Extend BigQuery functionality (#45)
- add extras per database engine (#50/#53). Postgres and Readshift is still included by default.
Note: It is recommended to always specifcy the extras for the database you use. - use client-side rendering for graphviz fallback (#51)
Bugfixes 🐛
- add all package files in wheel
- a proper error is now thrown when the user tries to look at the schema of a BigQuery database
Release 4.7.1 (Bigquery integration + fixes/enhancements)
Set fetch count 10000 to handle out of memory error
Set fetch-count 10000 for the copy_to_stdout_command
for PostgreSQLDB to handle out of memory error.