@@ -6,6 +6,29 @@ list](https://github.com/trinodb/trino-python-client/tags), the
6
6
[ README] ( https://github.com/trinodb/trino-python-client/blob/master/README.md )
7
7
and the [ PyPI page] ( https://pypi.org/project/trino/ ) .
8
8
9
+ ## Trino Python client 0.317.0
10
+
11
+ * Add support for creating tables containing ` JSON ` columns and reading and
12
+ writing to them with SQLAlchemy.
13
+ ([ #194 ] ( https://trinodb/trino-python-client/issues/194 ) )
14
+ * Properly propagate query failures to the client when using ` fetchone ` .
15
+ ([ #95 ] ( https://trinodb/trino-python-client/issues/95 ) )
16
+ * Fix queries returning a single row from sometimes appearing as failed on the
17
+ server. ([ #220 ] ( https://trinodb/trino-python-client/issues/220 ) )
18
+ * Fix query failures when using SQLAlchemy ` Table ` without a catalog name
19
+ provided. ([ #237 ] ( https://trinodb/trino-python-client/issues/237 ) )
20
+ * Fix errors when using prepared statements with Trino versions greater than or
21
+ equal to 398. ([ #242 ] ( https://trinodb/trino-python-client/issues/242 ) )
22
+
23
+ ### Breaking Changes
24
+
25
+ * Make the ` execute ` method of the cursor block until at-least one row is
26
+ received. This means users no longer need to call ` fetchone ` or ` fetchall ` to
27
+ make sure query actually starts executing on the Trino server. Note that
28
+ results still need to be consumed by calling ` fetchone ` or ` fetchall ` to make
29
+ sure query isn't considered idle and terminated on the server.
30
+ ([ #232 ] ( https://trinodb/trino-python-client/issues/232 ) )
31
+
9
32
## Trino Python client 0.316.0
10
33
11
34
* Add support for SQLAlchemy queries to access multiple catalogs by specifying
0 commit comments