Fix Trino parameterized type mapping

[shunki-fujita]

What type of PR is this?

Close: #7661

• Refactor
• Feature
• Bug Fix
• New Query Runner (Data Source)
• New Alert Destination
• Other

Description

Trino columns with parameterized types such as timestamp(0), timestamp(3), decimal(10,2), varchar(255), etc. are not correctly mapped to Redash column types. This causes timestamp columns to be displayed as epoch milliseconds in the UI when the result set contains NULL values.

How is this tested?

• Unit tests (pytest, jest)
• E2E Tests (Cypress)
• Manually
• N/A

The type determination for lines containing null is performed correctly.

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

[cubic-dev-ai]

1 issue found across 2 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="tests/query_runner/test_trino.py">

<violation number="1" location="tests/query_runner/test_trino.py:114">
P2: Parameterized fractional decimal is incorrectly asserted as `integer`, codifying wrong type semantics.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}