@@ -8,18 +8,22 @@ and the [PyPI page](https://pypi.org/project/trino/).
8
8
9
9
## Trino Python client 0.317.0
10
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 ) )
11
14
* Properly propagate query failures to the client when using ` fetchone ` .
12
15
([ #95 ] ( https://trinodb/trino-python-client/issues/95 ) )
13
- * Fix queries returning a single row from sometimes appearing as failed on the server.
14
- ([ #220 ] ( https://trinodb/trino-python-client/issues/220 ) )
16
+ * Fix queries returning a single row from sometimes appearing as failed on the
17
+ server. ([ #220 ] ( https://trinodb/trino-python-client/issues/220 ) )
15
18
16
19
### Breaking Changes
17
20
18
- * Make the ` execute ` method of the cursor block until at-least one row is received.
19
- This means users no longer need to call ` fetchone ` or ` fetchall ` to make sure query
20
- actually starts executing on the Trino server. Note that results still need to be consumed
21
- by calling ` fetchone ` or ` fetchall ` to make sure query isn't considered idle and terminated
22
- on the server. ([ #232 ] ( https://trinodb/trino-python-client/issues/232 ) )
21
+ * Make the ` execute ` method of the cursor block until at-least one row is
22
+ received. This means users no longer need to call ` fetchone ` or ` fetchall ` to
23
+ make sure query actually starts executing on the Trino server. Note that
24
+ results still need to be consumed by calling ` fetchone ` or ` fetchall ` to make
25
+ sure query isn't considered idle and terminated on the server.
26
+ ([ #232 ] ( https://trinodb/trino-python-client/issues/232 ) )
23
27
24
28
## Trino Python client 0.316.0
25
29
0 commit comments