Skip to content

UInt64 values get corrupted in JSON responses #111

Description

@rottensunday

Large UInt64 values come back wrong because they exceed JavaScript's max safe integer (2^53 - 1). A value like 1875924584784080993 becomes 1875924584784081000. This also happens for other large integer Clickhouse types.

I can manually wrap columns with toString() in every query, but if I don't know that it's necessary, I will just work with broken data.

I think this should be either specified somewhere in the docs/MCP description, or some automatic solution should be provided (for example wrap such types as a string).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions