TIME(P) is printed as TIME(3) for all P

[gw-vastdata]

Hi,

I'm using version 0.309.0 and probably have some client-side configuration issue, but I could not find it, so asking here.

Comparing SELECT TIME '01:02:03.456789'; executed from two clients connected to the same Trino 475 instance:
From trino==0.309.0:

[['01:02:03.457']]

From Trino 475 CLI:

01:02:03.456789

From the correct rounding it seems like a display configuration issue:

                        Create Table
-------------------------------------------------------------
 CREATE TABLE vast."bucket-for-array-times/aschema".atable (
    id integer,
    time_default array(time(3)),
    time_0 array(time(0)),
    time_3 array(time(3)),
    time_6 array(time(6)),
    time_9 array(time(9)),
    time_default_2 array(time(3)),
    time_0_2 array(time(0)),
    time_3_2 array(time(3)),
    time_6_2 array(time(6)),
    time_9_2 array(time(9))
 )
(1 row)

From 0.309.0 running SELECT * FROM vast."bucket-for-array-times/aschema".atable returns:

[1, ['23:59:59.999', '00:00:00.000', '01:02:03.001'], ['23:59:59.000', '00:00:00.000', '01:02:03.000'], ['23:59:59.999', '00:00:00.000', '01:02:03.001'], ['00:00:00.000', '00:00:00.000', '01:02:03.123'], ['00:00:00.000', '00:00:00.000', '01:02:03.123'], None, None, None, None, None]
[3, None, None, None, None, None, None, None, None, None, None]
[8, ['09:02:03.123'], ['09:05:06.000'], ['09:08:09.111'], ['09:11:12.124'], ['09:14:15.123'], None, None, None, None, None]
[7, None, None, None, None, None, ['23:59:59.999'], ['23:59:59.000'], ['23:59:59.999'], ['00:00:00.000'], ['00:00:00.000']]

From the official CLI:

trino> SELECT * FROM vast."bucket-for-array-times/aschema".atable;
 id |                time_default                |             time_0             |                   time_3                   |                       time_6                        |                            time_9                            | time_default_2 |  time_0_2  |    time_3_2    |     time_6_2      |       time_9_2       
----+--------------------------------------------+--------------------------------+--------------------------------------------+-----------------------------------------------------+--------------------------------------------------------------+----------------+------------+----------------+-------------------+----------------------
  1 | [23:59:59.999, 00:00:00.000, 01:02:03.001] | [23:59:59, 00:00:00, 01:02:03] | [23:59:59.999, 00:00:00.000, 01:02:03.001] | [23:59:59.999999, 00:00:00.000000, 01:02:03.123456] | [23:59:59.999999999, 00:00:00.000000000, 01:02:03.123456789] | NULL           | NULL       | NULL           | NULL              | NULL                 
  3 | NULL                                       | NULL                           | NULL                                       | NULL                                                | NULL                                                         | NULL           | NULL       | NULL           | NULL              | NULL                 
  8 | [09:02:03.123]                             | [09:05:06]                     | [09:08:09.111]                             | [09:11:12.123857]                                   | [09:14:15.123456789]                                         | NULL           | NULL       | NULL           | NULL              | NULL                 
  7 | NULL                                       | NULL                           | NULL                                       | NULL                                                | NULL                                                         | [23:59:59.999] | [23:59:59] | [23:59:59.999] | [23:59:59.999999] | [23:59:59.999999999] 
(4 rows)

FWIW this started during an upgrade from 462 to 475.

Thanks in advance :)

[wendigo]

Can't confirm that with the latest python client:

sql='SELECT TIME \'01:02:03.456789\''
conn = trino.dbapi.Connection(
  host='http://localhost',
  user='admin',
  port=8080,
  auth=None
)

cur = conn.cursor()
cur.execute(sql)

for row in cur:
    print(row)

 python3 test.py
[datetime.time(1, 2, 3, 456789)]

[wendigo]

trino-python-client 309 is really old and it's not supporting parametric datetime capability which means that all times/dates will be always precision 3. Use latest trino-python-client.