From d591848d150122ab97319c0085ceea55a5b30860 Mon Sep 17 00:00:00 2001 From: Ashhar Hasan Date: Thu, 22 Sep 2022 22:45:50 +0530 Subject: [PATCH] Add 0.317.0 release notes --- CHANGES.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/CHANGES.md b/CHANGES.md index eed58a31..dd3f9a36 100644 --- a/CHANGES.md +++ b/CHANGES.md @@ -6,6 +6,29 @@ list](https://github.com/trinodb/trino-python-client/tags), the [README](https://github.com/trinodb/trino-python-client/blob/master/README.md) and the [PyPI page](https://pypi.org/project/trino/). +## Trino Python client 0.317.0 + +* Add support for creating tables containing `JSON` columns and reading and + writing to them with SQLAlchemy. + ([#194](https://trinodb/trino-python-client/issues/194)) +* Properly propagate query failures to the client when using `fetchone`. + ([#95](https://trinodb/trino-python-client/issues/95)) +* Fix queries returning a single row from sometimes appearing as failed on the + server. ([#220](https://trinodb/trino-python-client/issues/220)) +* Fix query failures when using SQLAlchemy `TableClause` by not performing + catalog lookup. ([#237](https://trinodb/trino-python-client/issues/237)) +* Fix errors when using prepared statements with Trino versions greater than or + equal to 398. ([#242](https://trinodb/trino-python-client/issues/242)) + +### Breaking Changes + +* Make the `execute` method of the cursor block until at-least one row is + received. This means users no longer need to call `fetchone` or `fetchall` to + make sure query actually starts executing on the Trino server. Note that + results still need to be consumed by calling `fetchone` or `fetchall` to make + sure query isn't considered idle and terminated on the server. + ([#232](https://trinodb/trino-python-client/issues/232)) + ## Trino Python client 0.316.0 * Add support for SQLAlchemy queries to access multiple catalogs by specifying