Skip to content

Inserting data that can not be encoded as JSON should reject #13

@clue

Description

@clue

The ClickHouseClient currently uses JSON-encoded values when communicating with the ClickHouse server. If this encoding fails, it should properly reject the promise with an Exception.

Encoding most "normal" values works just fine, including UTF-8, newlines etc., but it's easy to run into this error when using different string encodings or binary data (not too common for ClickHouse afaict).

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinghelp wantedExtra attention is needednew featureNew feature or request

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions