Skip to content

Commit 8eef2b6

Browse files
committed
fixup! Add 0.317.0 release notes
1 parent de421c3 commit 8eef2b6

File tree

1 file changed

+11
-7
lines changed

1 file changed

+11
-7
lines changed

CHANGES.md

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,18 +8,22 @@ and the [PyPI page](https://pypi.org/project/trino/).
88

99
## Trino Python client 0.317.0
1010

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))
1114
* Properly propagate query failures to the client when using `fetchone`.
1215
([#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))
1518

1619
### Breaking Changes
1720

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))
2327

2428
## Trino Python client 0.316.0
2529

0 commit comments

Comments
 (0)