Make names of ROW datatype available in result set

[mdesmet]

Description

cur = trino_connection.cursor()
cur.execute("SELECT CAST(ROW(1, 2e0) AS ROW(x BIGINT, y DOUBLE))")
rows = cur.fetchall()

assert rows[0][0] == (1, 2.0)
assert rows[0][0].x == 1
assert rows[0][0].y == 2.0

cur = trino_connection.cursor()
cur.execute("SELECT CAST(ROW(1, ROW(1, 2e0)) AS ROW(x BIGINT, y ROW(x BIGINT, y DOUBLE)))")
rows = cur.fetchall()

assert rows[0][0] == (1, (1, 2.0))
assert rows[0][0].x == 1
assert rows[0][0].y.x == 1
assert rows[0][0].y.y == 2.0

Non-technical explanation

Release notes

( ) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
(x) Release notes are required, with the following suggested text:

* Make names of ROW datatype available in result set

Fixes #338

[mdesmet]

@hashhar: i didn't change the repr it still uses tuple's implementation. Do you think we should also adapt to show the attributes?

[mdesmet]

I also changed the __repr__ to also include attributes. I think that will be beneficial for debugging purposes.

[hashhar]

@mdesmet Did you forget to push some changes? I don't see any after your comment.

[Raghav-254]

Hi folks, when are you planning to release the new version 0.323.0.

[hashhar]

I plan to do a release sometime this week. There's a few PRs we're waiting for.

[Raghav-254]

Great
Currently at Linkedin we are using trino-python-client version 0.306.0 and for one of the column we are getting it's value as below

But now after upgrading it to 0.322.0, the output doesn't seem to be correct.

It seems that it is not handling the special characters properly. Can you please check this issue as well?

It is also giving the below error sometimes
Unsupported UTF-8 sequence length when encoding string

[hashhar]

@Raghav-254 Could you file an issue with some reproduction steps? At-least having the table DDL (or at-least data-type for the problematic column) + some snippet of how you use the client would be helpful.

[Raghav-254]

Hi @hashhar, thanks for responding so quickly.
I have opened up this issue: #355 including the steps to reproduce it.
Regards,
Raghav Mittal