questdb / questdb/ui

Web console doesn't always highlight correct error position

Open
#40 2 comments 0 reactions 1 assignee View on GitHub

@emrberk is already working on this.

Since Jul 7, 2025.

bug Severity: 2 web-console
Dominant language
TypeScript
Stars
29
Forks
39
Avg merge
4d 11h
Merged PRs (30d)
4

Description

Describe the bug

For some SQLs web console doesn't mark proper error position returned by backend .

To reproduce
  1. Open web console
  2. Execute
    select * from long_sequence(1) where cast(x as timestamp) = '2012-04-12T12:00:0A'
  3. Check that error marker is at start of line
Expected Behavior

Web console should mark problmatic timestamp literal - either whole or start or end.

Environment
- **QuestDB version**: latest 6.2.1 master
- **OS**: Windows
- **Browser**: Chrome
Additional context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.