← ClickHouseCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to ClickHouse
Snapshot Sep 30, 2026 · 22:50 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "clickhouse-js-node-troubleshooting",
"description": "Troubleshoot and resolve common issues with the ClickHouse Node.js client (@clickhouse/client). Use this skill whenever a user reports errors, unexpected behavior, or configuration questions involving the Node.js client specifically — including socket hang-up errors, Keep-Alive problems, stream handling issues, data type mismatches, read-only user restrictions, proxy/TLS setup problems, or long-running query timeouts. Trigger even when the user hasn't precisely named the issue; vague symptoms like \"my inserts keep failing\" or \"connection drops randomly\" in a Node.js context are strong signals to use this skill. Do NOT use for browser/Web client issues.",
"included_files": [
{
"relative_path": "reference/compression.md",
"size_in_bytes": 1456
},
{
"relative_path": "reference/data-types.md",
"size_in_bytes": 5075
},
{
"relative_path": "reference/logging.md",
"size_in_bytes": 1463
},
{
"relative_path": "reference/proxy-pathname.md",
"size_in_bytes": 1147
},
{
"relative_path": "reference/query-format-clause.md",
"size_in_bytes": 2576
},
{
"relative_path": "reference/query-params.md",
"size_in_bytes": 2871
},
{
"relative_path": "reference/readonly-users.md",
"size_in_bytes": 1044
},
{
"relative_path": "reference/socket-hangup.md",
"size_in_bytes": 10170
},
{
"relative_path": "reference/tls.md",
"size_in_bytes": 3125
}
],
"skill_md_contents": "---\nname: clickhouse-js-node-troubleshooting\ndescription: >\n Troubleshoot and resolve common issues with the ClickHouse Node.js client\n (@clickhouse/client). Use this skill whenever a user reports errors, unexpected\n behavior, or configuration questions involving the Node.js client specifically —\n including socket hang-up errors, Keep-Alive problems, stream handling issues, data\n type mismatches, read-only user restrictions, proxy/TLS setup problems, or long-running\n query timeouts. Trigger even when the user hasn't precisely named the issue; vague\n symptoms like \"my inserts keep failing\" or \"connection drops randomly\" in a Node.js\n context are strong signals to use this skill. Do NOT use for browser/Web client issues.\n---\n\n# ClickHouse Node.js Client Troubleshooting\n\nReference: https://clickhouse.com/docs/integrations/javascript\n\n> **⚠️ Node.js runtime only.** This skill covers the `@clickhouse/client` package running in a **Node.js runtime** exclusively — including **Next.js Node runtime** API routes, React Server Components, Server Actions, and standard Node.js processes. Do **not** apply this skill to browser client components, Web Workers, **Next.js Edge runtime**, Cloudflare Workers, or any usage of `@clickhouse/client-web`. For browser/edge environments, the correct package is `@clickhouse/client-web`.\n\n---\n\n## How to Use This Skill\n\n1. **Identify the issue** — match symptoms to the Issue Index below and read the corresponding reference file.\n2. **Lead with the diagnosis** — explain what's likely causing the issue before giving the fix.\n3. **Note version constraints** — flag if a fix requires a minimum client version and check it against what the user provided.\n4. **Ask only what's missing** — if the fix is version-dependent and you don't know their version, ask; otherwise help immediately.\n\n---\n\n## Issue Index\n\nIdentify the user's issue from the list below and read the corresponding reference file for detailed troubleshooting steps.\n\n| Issue | Symptoms | Reference file |\n| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- |\n| **Socket Hang-Up / ECONNRESET** | `socket hang up`, `ECONNRESET`, intermittent connection drops, long-running queries timing out | `reference/socket-hangup.md` |\n| **Data Type Mismatches** | Large integers returned as strings, decimal precision loss, Date/DateTime insertion failures, `CANNOT_PARSE_INPUT_ASSERTION_FAILED` inserting a UUID into a `UInt128` column | `reference/data-types.md` |\n| **Read-Only User Errors** | Errors when using response compression with `readonly=1` users | `reference/readonly-users.md` |\n| **Proxy / Pathname URL Confusion** | Wrong database selected, requests failing behind a proxy with a path prefix | `reference/proxy-pathname.md` |\n| **TLS / Certificate Errors** | TLS handshake failures, certificate verification issues, mutual TLS setup | `reference/tls.md` |\n| **Compression Not Working** | GZIP compression not activating for requests or responses | `reference/compression.md` |\n| **Logging Not Showing Anything** | No log output, need custom logger integration | `reference/logging.md` |\n| **Query Parameters Not Interpolated** | Parameterized queries not working, SQL injection concerns | `reference/query-params.md` |\n| **FORMAT Clause / `SHOW POLICIES` Errors** | Syntax error from a duplicate `FORMAT`, or `SHOW [ROW] POLICIES` failing even with a format provided | `reference/query-format-clause.md` |\n\n---\n\n## Still Stuck?\n\n- [JS client source + full examples](https://github.com/ClickHouse/clickhouse-js/tree/main/examples)\n- [ClickHouse JS client docs](https://clickhouse.com/docs/integrations/javascript)\n- [ClickHouse supported formats](https://clickhouse.com/docs/interfaces/formats)\n"
}SHA-256: 0d1dfe8f016b78fd81562b81e8f347179777d174d92473bad4acf9e2e6355912